On Mon, Dec 05, 2011 at 01:39:37PM +0800, Liu ping fan wrote:
On Sun, Dec 4, 2011 at 8:10 PM, Gleb Natapov g...@redhat.com wrote:
On Sun, Dec 04, 2011 at 07:53:37PM +0800, Liu ping fan wrote:
On Sat, Dec 3, 2011 at 2:26 AM, Jan Kiszka jan.kis...@siemens.com wrote:
On 2011-12-02 07:26, Liu
multiple queue virtio-net: flow steering through host/guest cooperation
Hello all:
This is a rough series adds the guest/host cooperation of flow
steering support based on Krish Kumar's multiple queue virtio-net
driver patch 3/3 (http://lwn.net/Articles/467283/).
This idea is simple, the
This patch enables the ability to pass the rxhash value to guest
through vnet_hdr. This is useful for guest when it wants to cooperate
with virtual device to steer a flow to dedicated guest cpu.
This feature is negotiated through VIRTIO_NET_F_GUEST_RXHASH.
Signed-off-by: Jason Wang
This patch adds a simple flow director to tun/tap device. It is just a
page that contains the hash to queue mapping which could be changed by
user-space. The backend (tap/macvtap) would query this table to get
the desired queue of a packets when it send packets to userspace.
The page address were
Signed-off-by: Jason Wang jasow...@redhat.com
---
drivers/net/macvlan.c |4
drivers/net/macvtap.c | 36 ++--
include/linux/if_macvlan.h |1 +
3 files changed, 39 insertions(+), 2 deletions(-)
diff --git a/drivers/net/macvlan.c
Device specific irq configuration may be need in order to do some
optimization. So a new configuration is needed to get the irq of a
virtqueue.
Signed-off-by: Jason Wang jasow...@redhat.com
---
drivers/lguest/lguest_device.c |8
drivers/s390/kvm/kvm_virtio.c |6 ++
In order to let the packets of a flow to be passed to the desired
guest cpu, we can co-operate with devices through programming the flow
director which was just a hash to queue table.
This kinds of co-operation is done through the accelerate RFS support,
a device specific flow sterring method
As it turned out, a windowsXP machine does not work in
qemu-kvm = 0.15 (it loses network and USB entirely)
if it is using Standard PC HAL. In 0.14 it worked
fine, but not in 0.14 (I haven't tried any in-between
versions yet).
There are several HAL types available in winXP: these
are Uniprocessor
Currently custom rootfs init is built along with the main KVM tools executable
and is copied into custom rootfs directories when they are created with
'kvm setup'. The problem there is that if the init code changes, they have
to be manually copied to custom rootfs directories.
Instead, this patch
On Mon, Dec 05, 2011 at 11:22:11AM +0200, Sasha Levin wrote:
+static int kvm_custom_stage2(void)
+{
+ char tmp[PATH_MAX], dst[PATH_MAX], *src;
+ const char *rootfs;
+ int r;
+
+ src = realpath(guest/init_stage2, NULL);
+ if (src == NULL)
+ return
On 12/05/2011 07:29 AM, Liu ping fan wrote:
like this,
#define kvm_for_each_vcpu(idx, cnt, vcpup, kvm) \
for (idx = 0, cnt = 0, vcpup = kvm_get_vcpu(kvm, idx); \
cnt atomic_read(kvm-online_vcpus) \
idx KVM_MAX_VCPUS; \
idx++, (vcpup == NULL)?:cnt++,
On Mon, Dec 05, 2011 at 11:30:51AM +0200, Avi Kivity wrote:
On 12/05/2011 07:29 AM, Liu ping fan wrote:
like this,
#define kvm_for_each_vcpu(idx, cnt, vcpup, kvm) \
for (idx = 0, cnt = 0, vcpup = kvm_get_vcpu(kvm, idx); \
cnt atomic_read(kvm-online_vcpus) \
idx
On 12/05/2011 02:10 AM, Rusty Russell wrote:
On Sun, 04 Dec 2011 17:16:59 +0200, Avi Kivity a...@redhat.com wrote:
On 12/04/2011 05:11 PM, Michael S. Tsirkin wrote:
There's also the used ring, but that's a
mistake if you have out of order completion. We should have used
copying.
On 12/05/2011 11:42 AM, Gleb Natapov wrote:
On Mon, Dec 05, 2011 at 11:30:51AM +0200, Avi Kivity wrote:
On 12/05/2011 07:29 AM, Liu ping fan wrote:
like this,
#define kvm_for_each_vcpu(idx, cnt, vcpup, kvm) \
for (idx = 0, cnt = 0, vcpup = kvm_get_vcpu(kvm, idx); \
cnt
On 12/04/2011 11:38 PM, Jan Kiszka wrote:
It should be also possible to migrate from non-KVM device to KVM
version, different names would prevent that for ever.
It is (theoretically) possible with these patches as the vmstate names
are the same. KVM to TCG migration does not work right
On Mon, Dec 05, 2011 at 11:58:56AM +0200, Avi Kivity wrote:
On 12/05/2011 11:42 AM, Gleb Natapov wrote:
On Mon, Dec 05, 2011 at 11:30:51AM +0200, Avi Kivity wrote:
On 12/05/2011 07:29 AM, Liu ping fan wrote:
like this,
#define kvm_for_each_vcpu(idx, cnt, vcpup, kvm) \
for
On 12/05/2011 12:18 PM, Gleb Natapov wrote:
We can, but that's a bigger change.
Is it? I do not see a lot of accesses to vcpu array except those loops.
Well actually some of those loops have to go away and be replaced by a
hash lookup with apic id as key.
--
error compiling
On Mon, Dec 5, 2011 at 8:58 AM, Jason Wang jasow...@redhat.com wrote:
This patch adds a simple flow director to tun/tap device. It is just a
page that contains the hash to queue mapping which could be changed by
user-space. The backend (tap/macvtap) would query this table to get
the desired
On Mon, Dec 05, 2011 at 12:22:53PM +0200, Avi Kivity wrote:
On 12/05/2011 12:18 PM, Gleb Natapov wrote:
We can, but that's a bigger change.
Is it? I do not see a lot of accesses to vcpu array except those loops.
Well actually some of those loops have to go away and be replaced
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 03.12.2011 23:33, schrieb Jan Kiszka:
On 2011-12-03 20:00, Andreas Färber wrote:
Am 03.12.2011 12:17, schrieb Jan Kiszka:
diff --git a/hw/kvmclock.c b/hw/kvm/clock.c similarity index
96% rename from hw/kvmclock.c rename to hw/kvm/clock.c index
On Mon, Dec 5, 2011 at 8:59 AM, Jason Wang jasow...@redhat.com wrote:
+static int virtnet_set_fd(struct net_device *dev, u32 pfn)
+{
+ struct virtnet_info *vi = netdev_priv(dev);
+ struct virtio_device *vdev = vi-vdev;
+
+ if (virtio_has_feature(vdev, VIRTIO_NET_F_HOST_FD))
On 2011-12-05 11:01, Avi Kivity wrote:
On 12/04/2011 11:38 PM, Jan Kiszka wrote:
It should be also possible to migrate from non-KVM device to KVM
version, different names would prevent that for ever.
It is (theoretically) possible with these patches as the vmstate names
are the same. KVM to
Hi,
This patchset fixes some issues in cgroup_common.py library and adds 2 new
tests to cgroup-kvm test.
Please find the details in each patch.
Sent to upstream as pull req. 103:
https://github.com/autotest/autotest/pull/103
Regards,
Lukáš
--
To unsubscribe from this list: send the line
Tests the cpuset.cpus cgroup feature. It stresses all VM's CPUs
and changes the CPU affinity. Verifies correct behaviour.
* Add TestCpusetCpus test
* import cleanup
* private function names cleanup
---
client/tests/cgroup/cgroup_common.py |2 +
client/tests/kvm/tests/cgroup.py | 211
Tests the cpuset.cpus cgroup feature. It stresses all VM's CPUs
while switching between cgroups with different setting.
Signed-off-by: Lukas Doktor ldok...@redhat.com
---
client/tests/cgroup/cgroup_common.py |4 +
client/tests/kvm/tests/cgroup.py | 108 +-
* Move LoadPerCpu into cgroup_common.py (cgroup-kvm will need it too)
* [FIX] Use etraceback
* Code cleanup
---
client/tests/cgroup/cgroup.py| 79 ++
client/tests/cgroup/cgroup_common.py | 22 +
2 files changed, 35 insertions(+), 66 deletions(-)
On 12/05/2011 01:37 PM, Jan Kiszka wrote:
On 2011-12-05 11:01, Avi Kivity wrote:
On 12/04/2011 11:38 PM, Jan Kiszka wrote:
It should be also possible to migrate from non-KVM device to KVM
version, different names would prevent that for ever.
It is (theoretically) possible with these
On 2011-12-05 13:36, Avi Kivity wrote:
On 12/05/2011 01:37 PM, Jan Kiszka wrote:
On 2011-12-05 11:01, Avi Kivity wrote:
On 12/04/2011 11:38 PM, Jan Kiszka wrote:
It should be also possible to migrate from non-KVM device to KVM
version, different names would prevent that for ever.
It is
On Sat, 03 Dec 2011, Jan Kiszka wrote:
On 2011-12-02 22:27, Eric B Munson wrote:
On Fri, 02 Dec 2011, Jan Kiszka wrote:
On 2011-12-02 20:19, Eric B Munson wrote:
Often when a guest is stopped from the qemu console, it will report
spurious
soft lockup warnings on resume. There are
On 12/05/2011 02:47 PM, Jan Kiszka wrote:
(the memory API added unstable names, hopefully the QOM can take over
the stable ones and we'll have a good way to denote the unstable ones).
OK, maybe - or likely - we should make those device models have the same
names in QOM once
On 12/05/2011 11:21 AM, Michael Tokarev wrote:
As it turned out, a windowsXP machine does not work in
qemu-kvm = 0.15 (it loses network and USB entirely)
if it is using Standard PC HAL. In 0.14 it worked
fine, but not in 0.14 (I haven't tried any in-between
versions yet).
There are several
On 2011-12-05 14:14, Avi Kivity wrote:
On 12/05/2011 02:47 PM, Jan Kiszka wrote:
(the memory API added unstable names, hopefully the QOM can take over
the stable ones and we'll have a good way to denote the unstable ones).
OK, maybe - or likely - we should make those device models have the
On 12/05/2011 03:29 PM, Jan Kiszka wrote:
On 2011-12-05 14:14, Avi Kivity wrote:
On 12/05/2011 02:47 PM, Jan Kiszka wrote:
(the memory API added unstable names, hopefully the QOM can take over
the stable ones and we'll have a good way to denote the unstable ones).
OK, maybe - or
On 2011-12-05 14:35, Marcelo Tosatti wrote:
On Sat, Dec 03, 2011 at 12:45:51PM +0100, Jan Kiszka wrote:
I was referring to the relation between the IOCTL and kvmclock, but
IOCTL vs. kvm_run.
Jan
Ah, OK. Yes, we better characterize it as KVMCLOCK specific (a generic
guest is paused command
On 2011-12-05 14:36, Avi Kivity wrote:
On 12/05/2011 03:29 PM, Jan Kiszka wrote:
On 2011-12-05 14:14, Avi Kivity wrote:
On 12/05/2011 02:47 PM, Jan Kiszka wrote:
(the memory API added unstable names, hopefully the QOM can take over
the stable ones and we'll have a good way to denote the
Hi
Please send in any agenda items you are interested in covering.
Proposal (from Anthony):
1. A short introduction to each of the guest agents, what guests they
support, and what verbs they support.
2. A short description of key requirements from each party (oVirt,
libvirt, QEMU) for a
Currently custom rootfs init is built along with the main KVM tools executable
and is copied into custom rootfs directories when they are created with
'kvm setup'. The problem there is that if the init code changes, they have
to be manually copied to custom rootfs directories.
Instead, this patch
Signed-off-by: Sasha Levin levinsasha...@gmail.com
---
tools/kvm/builtin-run.c |3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/tools/kvm/builtin-run.c b/tools/kvm/builtin-run.c
index 9635c82..de3001e 100644
--- a/tools/kvm/builtin-run.c
+++ b/tools/kvm/builtin-run.c
@@
This patch adds a '--sandbox' argument when used in conjuction with a custom
rootfs, it allows running a script or an executable in the guest environment
by using executables and other files from the host.
This is useful when testing code that might cause problems on the host, or
to automate
This allows other commands to wrap 'kvm run' and use the parameters user
provides after a dash-dash for it's own use.
Signed-off-by: Sasha Levin levinsasha...@gmail.com
---
tools/kvm/builtin-run.c |7 ++-
1 files changed, 6 insertions(+), 1 deletions(-)
diff --git
This patch adds 'kvm sandbox' which is a wrapper on top of 'kvm run' which
allows the user to easily specify sandboxed command to run in a custom
rootfs guest.
Example usage:
kvm sandbox -d test_guest -k some_kernel -- do_something_in_guest
Suggested-by: Pekka Enberg
On Sat, 03 Dec 2011, Sasha Levin wrote:
On Tue, 2011-11-29 at 16:35 -0500, Eric B Munson wrote:
Now that we have a flag that will tell the guest it was suspended,
create an interface for that communication using a KVM ioctl.
Signed-off-by: Eric B Munson emun...@mgebm.net
Can it
On Fri, 4 Nov 2011 09:45:59 +0100
Jan Kiszka jan.kis...@siemens.com wrote:
pci_block_user_cfg_access was designed for the use case that a single
context, the IPR driver, temporarily delays user space accesses to the
config space via sysfs. This assumption became invalid by the time
On Mon, 14 Nov 2011 20:18:55 +0200
Michael S. Tsirkin m...@redhat.com wrote:
Add a flexible mechanism to specify virtio configuration layout, using
pci vendor-specific capability. A separate capability is used for each
of common, device specific and data-path accesses.
Warning: compiled
2011/12/2 Cam Macdonell c...@cs.ualberta.ca:
2011/11/30 Cam Macdonell c...@cs.ualberta.ca:
2011/11/30 Zang Hongyong zanghongy...@huawei.com:
Can this bug fix patch be applied yet?
Sorry, for not replying yet. I'll test your patch within the next day.
Have you confirmed the proper receipt
On Mon, 2011-12-05 at 16:58 +0800, Jason Wang wrote:
This patch adds a simple flow director to tun/tap device. It is just a
page that contains the hash to queue mapping which could be changed by
user-space. The backend (tap/macvtap) would query this table to get
the desired queue of a packets
Similarly, macvtap chould implement the ethtool {get,set}_rxfh_indir
operations.
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
--
To unsubscribe from
Often when a guest is stopped from the qemu console, it will report spurious
soft lockup warnings on resume. There are kernel patches being discussed that
will give the host the ability to tell the guest that it is being stopped and
should ignore the soft lockup warning that generates. This
This flag will be used to check if the vm was stopped by the host when a soft
lockup was detected. The host will set the flag when it stops the guest. On
resume, the guest will check this flag if a soft lockup is detected and skip
issuing the warning.
Signed-off-by: Eric B Munson
When a host stops or suspends a VM it will set a flag to show this. The
watchdog will use these functions to determine if a softlockup is real, or the
result of a suspended VM.
Signed-off-by: Eric B Munson emun...@mgebm.net
Cc: mi...@redhat.com
Cc: h...@zytor.com
Cc: a...@arndb.de
Cc:
Changes from V4:
Rename KVM_GUEST_PAUSED to KVMCLOCK_GUEST_PAUSED
Add description of KVMCLOCK_GUEST_PAUSED ioctl to api.txt
Changes from V3:
Include CC's on patch 3
Drop clear flag ioctl and have the watchdog clear the flag when it is reset
Changes from V2:
A new kvm functions defined in
A suspended VM can cause spurious soft lockup warnings. To avoid these, the
watchdog now checks if the kernel knows it was stopped by the host and skips
the warning if so. When the watchdog is reset successfully, clear the guest
paused flag.
Signed-off-by: Eric B Munson emun...@mgebm.net
Cc:
On 05.12.2011 17:28, Avi Kivity wrote:
[]
I haven't debugged further yet, -- because it were
not easy to find out what was causing the regression
and how to reproduce it, and also because I don't think
it is the right HAL for qemu-kvm guest anyway.
It's not, but the regression indicates we
On Mon, Dec 05, 2011 at 11:16:05AM -0800, Jesse Barnes wrote:
On Mon, 14 Nov 2011 20:18:55 +0200
Michael S. Tsirkin m...@redhat.com wrote:
Add a flexible mechanism to specify virtio configuration layout, using
pci vendor-specific capability. A separate capability is used for each
of
Signed-off-by: Eric B Munson emun...@mgebm.net
Cc: mi...@redhat.com
Cc: h...@zytor.com
Cc: a...@arndb.de
Cc: ry...@linux.vnet.ibm.com
Cc: aligu...@us.ibm.com
Cc: mtosa...@redhat.com
Cc: jeremy.fitzhardi...@citrix.com
Cc: levinsasha...@gmail.com
Cc: Jan Kiszka jan.kis...@siemens.com
Cc:
Now that we have a flag that will tell the guest it was suspended, create an
interface for that communication using a KVM ioctl.
Signed-off-by: Eric B Munson emun...@mgebm.net
Cc: mi...@redhat.com
Cc: h...@zytor.com
Cc: a...@arndb.de
Cc: ry...@linux.vnet.ibm.com
Cc: aligu...@us.ibm.com
Cc:
On Mon, 2011-12-05 at 16:59 +0800, Jason Wang wrote:
In order to let the packets of a flow to be passed to the desired
guest cpu, we can co-operate with devices through programming the flow
director which was just a hash to queue table.
This kinds of co-operation is done through the
Hello,
I am struggling with repeatable full hardware locks when running 8-12 KVM vms.
At some point before the hard lock I get a inconsistent lock state warning. An
example of this can be found here:
http://pastebin.com/8wKhgE2C
After that the server continues to run for a while and then
On Wed, Nov 30, 2011 at 02:29:39PM +0530, Raghavendra K T wrote:
Add debugfs support to print u32-arrays in debugfs. Move the code from Xen to
debugfs
to make the code common for other users as well.
Signed-off-by: Srivatsa Vaddagiri va...@linux.vnet.ibm.com
Signed-off-by: Suzuki Poulose
subscribe kvm
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, Nov 30, 2011 at 02:30:38PM +0530, Raghavendra K T wrote:
This patch extends Linux guests running on KVM hypervisor to support
pv-ticketlocks.
During smp_boot_cpus paravirtualied KVM guest detects if the hypervisor has
required feature (KVM_FEATURE_KICK_VCPU) to support
Hi,
This patch series rearranges and tidies various parts of kvmtool to pave the way
for the addition of support for another architecture -- SPAPR PPC64. A second
patch series will follow to present the PPC64 support.
kvmtool is extremely x86-specific, so a fair chunk of refactoring into
Not every architecture has an i8042 kbd controller, so only use this when
building for x86.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/Makefile |2 +-
tools/kvm/builtin-run.c |2 ++
2 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/tools/kvm/Makefile
This patch adds an 'I' parameter to override the default kernel include path of
'../../include'.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/Makefile |9 +++--
1 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/tools/kvm/Makefile b/tools/kvm/Makefile
index
The checks for optional libraries build code to perform the tests, so should
respect certain CFLAGS -- in particular, -m64 so we check for 64bit libraries if
they're required.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/Makefile | 86
On LP64 systems our u64s are just longs; remove the %llx'es in favour of PRIx64
etc.
This patch also adds CFLAGS to the final link, so that any -m64 is obeyed when
linking, too.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/Makefile |2 +-
tools/kvm/builtin-run.c | 14
This patch creates a new function in x86/kvm-cpu.c, kvm_cpu__handle_exit(), in
which arch-specific exit reasons can be handled outside of the common runloop.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/include/kvm/kvm-cpu.h |2 ++
tools/kvm/kvm-cpu.c | 10 --
Architectures can recommend/count/determine number of CPUs differently, so move
this out of generic code.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/kvm.c | 30 --
tools/kvm/x86/kvm.c | 30 ++
2 files changed, 30
kvm_cpu__run() currently die()s if KVM_RUN returns non-zero. Some architectures
may return positive values in non-error cases, whereas real errors are always
negative return values. Check for those instead.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/kvm-cpu.c |2 +-
1 files
Currently, the SIGALRM handler calls device poll functions (for serial, virtio
console) directly. Which devices are present and which require polling is a
system-specific decision, so create a new function called from common code
move the x86-specific poll calls into it.
Signed-off-by: Matt
Fix a missing include.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/include/kvm/term.h |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/tools/kvm/include/kvm/term.h b/tools/kvm/include/kvm/term.h
index 37ec731..938c26f 100644
--- a/tools/kvm/include/kvm/term.h
Fix a missing include.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/kvm.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/tools/kvm/kvm.c b/tools/kvm/kvm.c
index e526483..33243f1 100644
--- a/tools/kvm/kvm.c
+++ b/tools/kvm/kvm.c
@@ -8,6 +8,7 @@
#include
Different systems will want different base kernel commandlines, e.g. non-x86
systems probably don't need noapic, i8042.* etc., so set the commandline up in
arch-specific code. Then, if the resulting commandline is empty, don't strcat a
space onto the front.
Signed-off-by: Matt Evans
This patch paves the way for adding a hypervisor console, useful on systems that
support one out of the box yet don't have either serial port or virtio console
support (e.g. kernels expecting POWER SPAPR).
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/builtin-run.c |8 ++--
term_getc()'s int c has one byte written into it (at its lowest address) by
read_in_full(). This is expected to be the least significant byte, but that
isn't the case on BE! Use correct type, unsigned char. A similar issue exists
in term_getc_iov(), which needs to write a char to the iov rather
cpios are valid as initrds too, so allow them through the check.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/kvm.c |8 +---
1 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/tools/kvm/kvm.c b/tools/kvm/kvm.c
index 33243f1..457de1a 100644
--- a/tools/kvm/kvm.c
+++
This patch passes the initrd fd and commandline to load_flat_binary(), which may
be used to load both the kernel an initrd (stashing or inserting the
commandline as appropriate) in the same way that load_bzimage() does. This is
especially useful when load_bzimage() is unused for a particular
CONFIG_HAS_BFD is optional, symbol.c inclusion is optional -- so make its init
call dependent on CONFIG_HAS_BFD.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/builtin-run.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/tools/kvm/builtin-run.c
Re-arrange pci__init() in builtin-run such that it comes before devices are
initialised.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/builtin-run.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/kvm/builtin-run.c b/tools/kvm/builtin-run.c
index
Currently some devices (in this case kbd, fb, vesa) are initialised after
CPU/firmware setup. On some platforms (e.g. PPC) kvm__arch_setup_firmware() may
be making a device tree. Any devices added after this point will be missed!
Tiny refactor of builtin-run.c, moving timer start, firmware
IRQ init may involve per-CPU setup/allocation of resources, so make sure
kvm-nrcpus is initialised before calling irq__init().
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/builtin-run.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/kvm/builtin-run.c
Some architectures may want to use hugetlbfs to mmap() their guest memory, so
allow a path to be specified on the commandline and pass it to kvm__arch_init().
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/builtin-run.c |4 +++-
tools/kvm/include/kvm/kvm.h |4 ++--
Other pieces of kvmtool may be interested in PCI_MAX_DEVICES.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/include/kvm/pci.h |1 +
tools/kvm/pci.c |1 -
2 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/tools/kvm/include/kvm/pci.h
vesa, pci-shmem and virtio-pci devices need to set up config space with
little-endian conversions (as config space is LE). The pci_config_address
bitfield also needs to be reversed when building on BE systems.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/hw/pci-shmem.c | 23
The field size is currently wrong, read into a 32bit word instead of 16. This
casues trouble when BE.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/virtio/pci.c |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/tools/kvm/virtio/pci.c b/tools/kvm/virtio/pci.c
The BAR addresses are set up fine, but missed the bar_size[] array which is now
updated correspondingly.
Use PCI_IO_SIZE instead of '0x100'.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/virtio/pci.c |7 +--
1 files changed, 5 insertions(+), 2 deletions(-)
diff --git
This allows config space access in a more natural manner than clunky x86 IO
ports,
and is useful for other architectures.
Furthermore, the actual registers were only accessed in 32bit chunks; other
systems (e.g. PPC) allow smaller accesses so that, for example, the 16-bit
config field can be
pci_get_io_space_block() used to grab addresses from
KVM_32BIT_GAP_START + 0x100, which is x86-specific. Create a new define,
KVM_PCI_MMIO_AREA, to specify a bus address these allocations can come from.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/pci.c |
Different architectures will deal with MMIO exits differently. For example,
KVM_EXIT_IO is x86-specific, and I/O cycles are often synthesisted by steering
into windows in PCI bridges on other architectures.
This patch moves the IO/MMIO exit code from the main runloop into x86/kvm-cpu.c
This patch adds a new arch directory, powerpc, basic file structure, register
setup and where necessary stubs out arch-specific functions (e.g. interrupts,
runloop exits) that later patches will provide. The target is an
SPAPR-compliant PPC64 machine (i.e. pSeries); there is no support for PPC32
The generated DT is the bare minimum structure required for SPAPR (on which
subsequent patches for VIO, XICS, PCI etc. will build); root node, cpus, memory.
Some aspects are currently hardwired for simplicity, for example advertised
page sizes, HPT size, SLB size, VMX/DFP, etc. Future support of
Hi,
This set of patches builds upon the prep-work of the previous set and adds
support to kvmtool for PPC64 SPAPR-based guests, i.e. an environment akin to an
LPAR on IBM's pSeries machines.
This support is not yet fully-featured but, in a basic state, works well.
The guests have a functional
This patch adds the basic structure for HV calls, their registration and some of
the simpler calls. A similar layout for RTAS calls is also added, again with
some of the simpler RTAS calls used by the guest. The SPAPR RTAS stub is
generated inline. Also, nodes for RTAS are added to the device
This adds the console code, plus VIO HV terminal nodes are added to
the device tree so the guest kernel will pick it up.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/Makefile |1 +
tools/kvm/powerpc/kvm.c | 31
tools/kvm/powerpc/spapr_hvcons.c
This patch adds XICS emulation code (heavily borrowed from QEMU), and wires
this into kvm_cpu__irq() to fire a CPU IRQ via KVM. A device tree entry is
also added. IPIs work, xics_alloc_irqnum() is added to allocate an external
IRQ (which will later be used by the PHB PCI code) and finally,
This provides the PCI bridge, definitions for the address layout of the windows
and wires in IRQs. Once PCI devices are all registered, they are enumerated and
DT nodes generated for each.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/powerpc/include/kvm/kvm-arch.h |3 +
This is the final piece of the puzzle for PPC SPAPR PCI; this
function splits MMIO accesses into the two PHB windows directs
things to MMIO/IO emulation as appropriate.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/Makefile |1 +
tools/kvm/powerpc/kvm-cpu.c | 34
PPC KVM doesn't yet support ioeventfds, so don't bomb out/die. virtio-pci is
able to function if it instead uses normal IO port notification.
Signed-off-by: Matt Evans m...@ozlabs.org
---
tools/kvm/include/kvm/ioeventfd.h |3 ++-
tools/kvm/ioeventfd.c | 12 +---
On Mon, 05 Dec 2011 11:52:54 +0200, Avi Kivity a...@redhat.com wrote:
On 12/05/2011 02:10 AM, Rusty Russell wrote:
On Sun, 04 Dec 2011 17:16:59 +0200, Avi Kivity a...@redhat.com wrote:
On 12/04/2011 05:11 PM, Michael S. Tsirkin wrote:
There's also the used ring, but that's a
On 06/12/11 14:35, Matt Evans wrote:
This patch series rearranges and tidies various parts of kvmtool to pave the
way
for the addition of support for another architecture -- SPAPR PPC64. A second
patch series will follow to present the PPC64 support.
I forgot to mention, of course, that
1 - 100 of 164 matches
Mail list logo
