On Friday 12 November 2010 01:29:29 Jesse Barnes wrote:
On Thu, 11 Nov 2010 15:46:55 +0800
Sheng Yang sh...@linux.intel.com wrote:
Then we can use it instead of magic number 1.
Reviewed-by: Hidetoshi Seto seto.hideto...@jp.fujitsu.com
Cc: Matthew Wilcox wi...@linux.intel.com
Cc:
On Mon, Nov 15, 2010 at 09:53:50AM +0200, Michael S. Tsirkin wrote:
On Mon, Nov 15, 2010 at 09:40:08AM +0200, Gleb Natapov wrote:
On Sun, Nov 14, 2010 at 10:40:33PM -0500, Kevin O'Connor wrote:
On Sun, Nov 14, 2010 at 05:39:41PM +0200, Gleb Natapov wrote:
+/*
+ * This function
On Monday 15 November 2010 16:03:53 Michael S. Tsirkin wrote:
On Mon, Nov 15, 2010 at 03:48:46PM +0800, Sheng Yang wrote:
On Monday 15 November 2010 15:42:50 Michael S. Tsirkin wrote:
On Mon, Nov 15, 2010 at 03:37:21PM +0800, Sheng Yang wrote:
We can back to them if there is someone
On Sun, Nov 14, 2010 at 10:50:13PM +, Blue Swirl wrote:
On Sun, Nov 14, 2010 at 3:39 PM, Gleb Natapov g...@redhat.com wrote:
Signed-off-by: Gleb Natapov g...@redhat.com
---
hw/fw_cfg.c | 14 ++
hw/fw_cfg.h | 4 +++-
sysemu.h | 1 +
vl.c | 51
linux_...@proinbox.com writes:
Hi Everyone,
I'm impressed with all the activity I see here since joining the list
this year.
It helps to reinforce that I chose the right technology. Thanks.
The -device method vhost=on option recently became available to us at
the ProxmoxVE project I'm
On 11/15/2010 09:24 AM, lidong chen wrote:
the address is the Region 1 of virtio_net.
why virtio_net use this address caused ept violation?
It's probably the MSIX mask bit. Older kernels program this bit twice
on every interrupt. Newer kernels do this much less frequently. Try
with a new
We need to query the entry later.
Signed-off-by: Sheng Yang sh...@linux.intel.com
---
include/linux/kvm_host.h |2 ++
virt/kvm/irq_comm.c | 20
2 files changed, 22 insertions(+), 0 deletions(-)
diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h
Change from v4:
1. Rebased on latest KVM
2. Fix minor comments.
3. Drop big-endian patch because unable to guarantee the correctless. Add TODO
for it.
Change from v3:
1. Re-design the userspace API.
2. Add big-endian support for msix_mmio_read/write()(untested!)
Change from v2:
1. Move all mask
This patch enable per-vector mask for assigned devices using MSI-X.
This patch provided two new APIs: one is for guest to specific device's MSI-X
table address in MMIO, the other is for userspace to get information about mask
bit.
All the mask bit operation are kept in kernel, in order to
Reuse KVM_DEV_ASSIGN_ENABLE_IOMMU for an in-kernel struct didn't make much
sense.
Signed-off-by: Sheng Yang sh...@linux.intel.com
---
include/linux/kvm_host.h |1 +
virt/kvm/assigned-dev.c |7 ---
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git
Then we can use it instead of magic number 1.
Reviewed-by: Hidetoshi Seto seto.hideto...@jp.fujitsu.com
Acked-by: Jesse Barnes jbar...@virtuousgeek.org
Cc: Matthew Wilcox wi...@linux.intel.com
Cc: linux-...@vger.kernel.org
Signed-off-by: Sheng Yang sh...@linux.intel.com
---
drivers/pci/msi.c
Then it can be used by others.
Reviewed-by: Hidetoshi Seto seto.hideto...@jp.fujitsu.com
Reviewed-by: Matthew Wilcox wi...@linux.intel.com
Acked-by: Jesse Barnes jbar...@virtuousgeek.org
Cc: linux-...@vger.kernel.org
Signed-off-by: Sheng Yang sh...@linux.intel.com
---
drivers/pci/msi.h|
On 11/15/2010 07:41 AM, Xiao Guangrong wrote:
On 11/14/2010 06:56 PM, Avi Kivity wrote:
On 11/12/2010 12:34 PM, Xiao Guangrong wrote:
We can past the page fault to guest directly if gpte's reserved
is set
How can that work? shadow_notrap_nonpresent_pte causes a fault with
This patch enable per-vector mask for assigned devices using MSI-X.
This patch provided two new APIs: one is for guest to specific device's MSI-X
table address in MMIO, the other is for userspace to get information about mask
bit.
All the mask bit operation are kept in kernel, in order to
On 11/15/2010 07:25 AM, Xiao Guangrong wrote:
On 11/14/2010 06:46 PM, Avi Kivity wrote:
On 11/12/2010 08:50 AM, Xiao Guangrong wrote:
Retry #PF for softmmu only when the current vcpu has the same
root shadow page as the time when #PF occurs. it means they
have same paging environment
On 11/15/2010 05:30 PM, Avi Kivity wrote:
Yeah, this 'retry' is unnecessary if the process is killed, but this
case is infrequent, the most case is the process keeps running and try
to access the fault address later.
The problem is that if we retry in this case, we install an incorrect
On Mon, Nov 15, 2010 at 05:55:25PM +0800, Xiao Guangrong wrote:
On 11/15/2010 05:30 PM, Avi Kivity wrote:
Yeah, this 'retry' is unnecessary if the process is killed, but this
case is infrequent, the most case is the process keeps running and try
to access the fault address later.
The
On 11/15/2010 11:55 AM, Xiao Guangrong wrote:
Or another thread may have mmap()ed something else over the
same address.
The mmap virtual address is also visible for other threads since the
threads
have the same page table, so i think this case is the same as above?
Again,
The issue of d) is that there are multiple ways to inject MCE. Now one
software based, one APEI based, and maybe some others in the future.
They all use different interfaces. And as debug interface, there are not
considered kernel ABI too (some are in debugfs). So I think it is better
to use
On 11/15/2010 05:59 PM, Avi Kivity wrote:
On 11/15/2010 11:55 AM, Xiao Guangrong wrote:
Or another thread may have mmap()ed something else over the
same address.
The mmap virtual address is also visible for other threads since the
threads
have the same page table, so i
On Sun, Nov 14, 2010 at 09:33:06PM +, Blue Swirl wrote:
On Sun, Nov 14, 2010 at 3:39 PM, Gleb Natapov g...@redhat.com wrote:
Extend -option-rom command to have additional parameter ,bootindex=.
This patch is broken:
CCarm-softmmu/palm.o
/src/qemu/hw/palm.c: In function
These diffs to upstream should all date back to the days qemu-kvm
supported vga dirty logging with restricted/broken kvm kernel modules.
We no longer do, so there is no need for those workarounds. Even worse
they can trigger internal bug checks these days:
BUG: kvm_dirty_pages_log_change: invalid
On Sun, Nov 14, 2010 at 12:19 PM, Avi Kivity a...@redhat.com wrote:
On 11/14/2010 01:05 PM, Avi Kivity wrote:
I agree, but let's enable virtio-ioeventfd carefully because bad code
is out there.
Sure. Note as long as the thread waiting on ioeventfd doesn't consume too
much cpu, it will
[Wrong list, it's not upstream yet. I'm migrating the thread to kvm.]
Am 15.11.2010 12:33, Bernhard Kohl wrote:
This is necessary because during reboot of a VM the assigned devices
continue DMA transfers which causes memory corruption.
Signed-off-by: Thomas Ostler thomas.ost...@nsn.com
2010/11/15, Avi Kivity a...@redhat.com:
On 11/15/2010 09:24 AM, lidong chen wrote:
the address is the Region 1 of virtio_net.
why virtio_net use this address caused ept violation?
It's probably the MSIX mask bit. Older kernels program this bit twice
on every interrupt. Newer kernels do
I think the address maybe initialized in function virtio_pci_probe.
err = pci_request_regions(pci_dev, virtio-pci);
but i did not know when used this address.
2010/11/15, lidong chen chen.lidong.ker...@gmail.com:
2010/11/15, Avi Kivity a...@redhat.com:
On 11/15/2010 09:24 AM, lidong chen
On 11/15/2010 12:32 PM, Jan Kiszka wrote:
These diffs to upstream should all date back to the days qemu-kvm
supported vga dirty logging with restricted/broken kvm kernel modules.
We no longer do, so there is no need for those workarounds. Even worse
they can trigger internal bug checks these
On Mon, Nov 15, 2010 at 09:40:08AM +0200, Gleb Natapov wrote:
On Sun, Nov 14, 2010 at 10:40:33PM -0500, Kevin O'Connor wrote:
Why not just return a newline separated list that is null terminated?
Doing it like this will needlessly complicate firmware side. How do you
know how much memory
Am 15.11.2010 14:16, Avi Kivity wrote:
On 11/15/2010 12:32 PM, Jan Kiszka wrote:
These diffs to upstream should all date back to the days qemu-kvm
supported vga dirty logging with restricted/broken kvm kernel modules.
We no longer do, so there is no need for those workarounds. Even worse
they
On 11/15/2010 03:26 PM, Jan Kiszka wrote:
Am 15.11.2010 14:16, Avi Kivity wrote:
On 11/15/2010 12:32 PM, Jan Kiszka wrote:
These diffs to upstream should all date back to the days qemu-kvm
supported vga dirty logging with restricted/broken kvm kernel modules.
We no longer do, so there is
On Mon, Nov 15, 2010 at 08:26:35AM -0500, Kevin O'Connor wrote:
On Mon, Nov 15, 2010 at 09:40:08AM +0200, Gleb Natapov wrote:
On Sun, Nov 14, 2010 at 10:40:33PM -0500, Kevin O'Connor wrote:
Why not just return a newline separated list that is null terminated?
Doing it like this will
Installing Windows XP with seabios 0.6.1, immediately after the first
reboot, Windows hangs in protected mode instead of proceeding with
installation.
I'm bisecting this, but if anyone can point to a likely culprit, I can
try it first.
--
error compiling committee.c: too many arguments to
On Mon, Nov 15, 2010 at 03:36:25PM +0200, Gleb Natapov wrote:
Hmm BTW I do not see proper endianness
handling in FILE_DIR.
That's just me. Everything it OK there with endianness.
--
Gleb.
--
To unsubscribe from this list: send the line
New get_fw_dev_path callback will be used for build device path usable
by firmware in contrast to qdev qemu internal device path.
Signed-off-by: Gleb Natapov g...@redhat.com
---
hw/qdev.h |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/hw/qdev.h b/hw/qdev.h
index
Add fw_name to DeviceInfo to use in device path building. In
contrast to name fw_name should refer to functionality device
provides instead of particular device model like name does.
Signed-off-by: Gleb Natapov g...@redhat.com
---
hw/fdc.c|1 +
hw/ide/isa.c|1 +
hw/ide/qdev.c
Use device ioports to create unique device path.
Signed-off-by: Gleb Natapov g...@redhat.com
---
hw/isa-bus.c | 16
1 files changed, 16 insertions(+), 0 deletions(-)
diff --git a/hw/isa-bus.c b/hw/isa-bus.c
index c0ac7e9..c423c1b 100644
--- a/hw/isa-bus.c
+++ b/hw/isa-bus.c
I am using open firmware naming scheme to specify device path names.
In this version: fixed compilation problem, changed how device list
is passed into firmware.
Names look like this on pci machine:
/p...@i0cf8/i...@1,1/dr...@1/d...@0
/p...@i0cf8/i...@1/f...@03f1/flo...@1
Signed-off-by: Gleb Natapov g...@redhat.com
---
hw/pci.c | 108 -
1 files changed, 85 insertions(+), 23 deletions(-)
diff --git a/hw/pci.c b/hw/pci.c
index 962886e..114b435 100644
--- a/hw/pci.c
+++ b/hw/pci.c
@@ -43,12 +43,14 @@
Prints out mmio or pio used to access child device.
Signed-off-by: Gleb Natapov g...@redhat.com
---
hw/pci_host.c |2 ++
hw/sysbus.c | 30 ++
hw/sysbus.h |4
3 files changed, 36 insertions(+), 0 deletions(-)
diff --git a/hw/pci_host.c
Signed-off-by: Gleb Natapov g...@redhat.com
---
hw/fw_cfg.c | 15 +++
hw/fw_cfg.h |5 -
sysemu.h|1 +
vl.c| 49 +
4 files changed, 69 insertions(+), 1 deletions(-)
diff --git a/hw/fw_cfg.c b/hw/fw_cfg.c
If bootindex is specified on command line a string that describes device
in firmware readable way is added into sorted list. Later this list will
be passed into firmware to control boot order.
Signed-off-by: Gleb Natapov g...@redhat.com
---
block_int.h |4 +++-
hw/e1000.c |4
Ports on root hub will have NULL here. This is needed to reconstruct
path from device to its root hub to build device path.
Signed-off-by: Gleb Natapov g...@redhat.com
---
hw/usb-bus.c |3 ++-
hw/usb-hub.c |2 +-
hw/usb-musb.c |2 +-
hw/usb-ohci.c |2 +-
hw/usb-uhci.c |2 +-
Signed-off-by: Gleb Natapov g...@redhat.com
---
hw/ide/cmd646.c |4 ++--
hw/ide/internal.h |3 ++-
hw/ide/isa.c |2 +-
hw/ide/piix.c |4 ++--
hw/ide/qdev.c |3 ++-
hw/ide/via.c |4 ++--
6 files changed, 11 insertions(+), 9 deletions(-)
diff --git
Signed-off-by: Gleb Natapov g...@redhat.com
---
hw/usb-bus.c | 42 ++
1 files changed, 42 insertions(+), 0 deletions(-)
diff --git a/hw/usb-bus.c b/hw/usb-bus.c
index 256b881..8b4583c 100644
--- a/hw/usb-bus.c
+++ b/hw/usb-bus.c
@@ -5,11 +5,13 @@
Change fw_cfg_add_file() to get full file path as a parameter instead
of building one internally. Two reasons for that. First caller may need
to know how file is named. Second this moves policy of file naming out
from fw_cfg. Platform may want to use more then two levels of
directories for
Action that depends on fully initialized device model should register
with this notifier chain.
Signed-off-by: Gleb Natapov g...@redhat.com
---
sysemu.h |2 ++
vl.c | 15 +++
2 files changed, 17 insertions(+), 0 deletions(-)
diff --git a/sysemu.h b/sysemu.h
index
Signed-off-by: Gleb Natapov g...@redhat.com
---
hw/ide/qdev.c | 13 +
1 files changed, 13 insertions(+), 0 deletions(-)
diff --git a/hw/ide/qdev.c b/hw/ide/qdev.c
index 88ff657..01a181b 100644
--- a/hw/ide/qdev.c
+++ b/hw/ide/qdev.c
@@ -24,9 +24,12 @@
/*
Extend -option-rom command to have additional parameter ,bootindex=.
Signed-off-by: Gleb Natapov g...@redhat.com
---
hw/loader.c| 16 +++-
hw/loader.h|8
hw/multiboot.c |3 ++-
hw/ne2000.c|2 +-
hw/nseries.c |4 ++--
hw/palm.c |6
Store all io ports used by device in ISADevice structure.
Signed-off-by: Gleb Natapov g...@redhat.com
---
hw/cs4231a.c |1 +
hw/fdc.c |3 +++
hw/gus.c |4
hw/ide/isa.c |2 ++
hw/isa-bus.c | 25 +
hw/isa.h |4
On 11/15/2010 03:39 PM, Avi Kivity wrote:
Installing Windows XP with seabios 0.6.1, immediately after the first
reboot, Windows hangs in protected mode instead of proceeding with
installation.
I'm bisecting this, but if anyone can point to a likely culprit, I can
try it first.
Bisect
On 11/15/2010 05:04 PM, Avi Kivity wrote:
On 11/15/2010 03:39 PM, Avi Kivity wrote:
Installing Windows XP with seabios 0.6.1, immediately after the first
reboot, Windows hangs in protected mode instead of proceeding with
installation.
I'm bisecting this, but if anyone can point to a likely
On 11/15/2010 05:12 PM, Avi Kivity wrote:
That was premature, the real culprit (if I didn't mess up the bisect) is:
commit 6039fc55274deb7202060d08e0f23b9f3dcface4
Author: Kevin O'Connor ke...@koconnor.net
Date: Wed Aug 25 21:43:19 2010 -0400
Update qemu_cfg_read to use rep insb.
On 11/15/2010 05:34 PM, Avi Kivity wrote:
On 11/15/2010 05:12 PM, Avi Kivity wrote:
That was premature, the real culprit (if I didn't mess up the bisect)
is:
commit 6039fc55274deb7202060d08e0f23b9f3dcface4
Author: Kevin O'Connor ke...@koconnor.net
Date: Wed Aug 25 21:43:19 2010 -0400
On 11/15/2010 05:41 PM, Avi Kivity wrote:
I think it's a miscompile.
out/code16.o:
1a4: 3e ds
1a5: 6c insb (%dx),%es:(%edi)
Note no 66 prefix.
It isn't, that was random crap. All the insb() code is 32-bit.
--
error compiling committee.c:
On 11/15/2010 05:49 PM, Avi Kivity wrote:
On 11/15/2010 05:41 PM, Avi Kivity wrote:
I think it's a miscompile.
out/code16.o:
1a4: 3e ds
1a5: 6c insb (%dx),%es:(%edi)
Note no 66 prefix.
It isn't, that was random crap. All the insb() code
http://kortina94.com/mydocs.php
--
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
This patch introduce a fallback mechanism for old systems that do not
support utimensat(). This fix build failure with following warnings:
hw/virtio-9p-local.c: In function 'local_utimensat':
hw/virtio-9p-local.c:479: warning: implicit declaration of function
'utimensat'
With the latest git versions, e.g. 1.7.2.3, git still prints out
the tag info in addition to the requested format. So let's simply
fetch the first line from the output.
In addition I use the --pretty option instead of --format which
is not recognized in very old git versions, e.g. 1.5.5.6.
Hi Stefan,
thanks for your feedback. Yehuda and Sage have already committed some
pathes to our git repository.
What I'm not sure about is the rados_(de)initialization for multiple
rbd images. I suspect that _deinitialize should only be called for the
last rbd image.
Yehuda and Sage know
trace-cmd doesn't like trace_printk():
...-23775 [000] 26343.288803: kvm_emulate_insn: 0:f14e9: rep insb
...-23775 [000] 26343.288804: bprint: x86_emulate_insn :
(NO FORMAT FOUND at a0131460)
...-23775 [000] 26343.288807: bprint: x86_emulate_insn :
(NO
On Mon, Nov 15, 2010 at 9:04 AM, Christian Brunner
c.m.brun...@gmail.com wrote:
Hi Stefan,
thanks for your feedback. Yehuda and Sage have already committed some
pathes to our git repository.
What I'm not sure about is the rados_(de)initialization for multiple
rbd images. I suspect that
On Mon, 2010-11-15 at 19:09 +0200, Avi Kivity wrote:
trace-cmd doesn't like trace_printk():
...-23775 [000] 26343.288803: kvm_emulate_insn: 0:f14e9: rep insb
...-23775 [000] 26343.288804: bprint: x86_emulate_insn :
(NO FORMAT FOUND at a0131460)
...-23775 [000]
On 11/15/2010 07:11 PM, Steven Rostedt wrote:
On Mon, 2010-11-15 at 19:09 +0200, Avi Kivity wrote:
trace-cmd doesn't like trace_printk():
...-23775 [000] 26343.288803: kvm_emulate_insn: 0:f14e9: rep insb
...-23775 [000] 26343.288804: bprint: x86_emulate_insn :
(NO
Use register_device_unmigratable() to declare ourselves as
non-migratable.
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
hw/device-assignment.c | 15 +++
1 files changed, 15 insertions(+), 0 deletions(-)
diff --git a/hw/device-assignment.c b/hw/device-assignment.c
Am 15.11.2010 20:41, Alex Williamson wrote:
Use register_device_unmigratable() to declare ourselves as
non-migratable.
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
hw/device-assignment.c | 15 +++
1 files changed, 15 insertions(+), 0 deletions(-)
diff
Please send in any agenda items you are interested in covering.
thanks,
-chris
--
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 Mon, 2010-11-15 at 21:05 +0100, Jan Kiszka wrote:
Am 15.11.2010 20:41, Alex Williamson wrote:
Use register_device_unmigratable() to declare ourselves as
non-migratable.
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
hw/device-assignment.c | 15 +++
2010/11/15 Gleb Natapov g...@redhat.com:
On Sun, Nov 14, 2010 at 10:50:13PM +, Blue Swirl wrote:
On Sun, Nov 14, 2010 at 3:39 PM, Gleb Natapov g...@redhat.com wrote:
Signed-off-by: Gleb Natapov g...@redhat.com
---
hw/fw_cfg.c | 14 ++
hw/fw_cfg.h | 4 +++-
On Mon, 2010-11-15 at 13:08 +0100, Jan Kiszka wrote:
[Wrong list, it's not upstream yet. I'm migrating the thread to kvm.]
Am 15.11.2010 12:33, Bernhard Kohl wrote:
This is necessary because during reboot of a VM the assigned devices
continue DMA transfers which causes memory corruption.
Am 15.11.2010 21:38, Alex Williamson wrote:
On Mon, 2010-11-15 at 13:08 +0100, Jan Kiszka wrote:
[Wrong list, it's not upstream yet. I'm migrating the thread to kvm.]
Am 15.11.2010 12:33, Bernhard Kohl wrote:
This is necessary because during reboot of a VM the assigned devices
continue DMA
Am 15.11.2010 21:25, Alex Williamson wrote:
On Mon, 2010-11-15 at 21:05 +0100, Jan Kiszka wrote:
Am 15.11.2010 20:41, Alex Williamson wrote:
Use register_device_unmigratable() to declare ourselves as
non-migratable.
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
On Mon, 2010-11-15 at 23:04 +0100, Jan Kiszka wrote:
Am 15.11.2010 21:25, Alex Williamson wrote:
On Mon, 2010-11-15 at 21:05 +0100, Jan Kiszka wrote:
Am 15.11.2010 20:41, Alex Williamson wrote:
Use register_device_unmigratable() to declare ourselves as
non-migratable.
Signed-off-by:
Am 15.11.2010 23:25, Alex Williamson wrote:
On Mon, 2010-11-15 at 23:04 +0100, Jan Kiszka wrote:
Am 15.11.2010 21:25, Alex Williamson wrote:
On Mon, 2010-11-15 at 21:05 +0100, Jan Kiszka wrote:
Am 15.11.2010 20:41, Alex Williamson wrote:
Use register_device_unmigratable() to declare ourselves
Am 15.11.2010 22:55, Erik Brakkee wrote:
Jan Kiszka wrote:
Am 14.11.2010 14:21, Erik Brakkee wrote:
Jan Kiszka wrote:
Strange, should work. I would suggest to post your full kernel log,
maybe there is some enlightening message hidden.
I don't think it is a problem of your kernel
Use register_device_unmigratable() to declare ourselves as
non-migratable.
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
v2: Use dummy vmsd instead of dummy save_state
hw/device-assignment.c | 10 ++
1 files changed, 10 insertions(+), 0 deletions(-)
diff --git
Use register_device_unmigratable() to declare ourselves as
non-migratable.
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
v3: Use .name instead of repeating pci-assign
v2: Use dummy vmsd instead of dummy save_state
hw/device-assignment.c | 11 +++
1 files changed, 11
Am 16.11.2010 00:06, Alex Williamson wrote:
Use register_device_unmigratable() to declare ourselves as
non-migratable.
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
v2: Use dummy vmsd instead of dummy save_state
hw/device-assignment.c | 10 ++
1 files
On Tue, 2010-11-16 at 00:11 +0100, Jan Kiszka wrote:
Am 16.11.2010 00:06, Alex Williamson wrote:
Use register_device_unmigratable() to declare ourselves as
non-migratable.
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
v2: Use dummy vmsd instead of dummy save_state
Am 16.11.2010 00:24, Alex Williamson wrote:
On Tue, 2010-11-16 at 00:11 +0100, Jan Kiszka wrote:
Am 16.11.2010 00:06, Alex Williamson wrote:
Use register_device_unmigratable() to declare ourselves as
non-migratable.
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
v2: Use
On Mon, Nov 15, 2010 at 06:09:45PM +0200, Avi Kivity wrote:
On 11/15/2010 05:49 PM, Avi Kivity wrote:
On 11/15/2010 05:41 PM, Avi Kivity wrote:
I think it's a miscompile.
out/code16.o:
1a4: 3e ds
1a5: 6c insb (%dx),%es:(%edi)
Note no
Author: Max Asbock masb...@linux.vnet.ibm.com
Add command x-gpa2hva to translate guest physical address to host
virtual address. Because gpa to hva translation is not consistent, so
this command is only used for debugging.
The x-gpa2hva command provides one step in a chain of translations from
On Mon, Nov 15, 2010 at 03:36:25PM +0200, Gleb Natapov wrote:
On Mon, Nov 15, 2010 at 08:26:35AM -0500, Kevin O'Connor wrote:
On Mon, Nov 15, 2010 at 09:40:08AM +0200, Gleb Natapov wrote:
On Sun, Nov 14, 2010 at 10:40:33PM -0500, Kevin O'Connor wrote:
Why not just return a newline
Avi Kivity wrote:
On 11/14/2010 12:41 PM, Jan Kiszka wrote:
Am 14.11.2010 11:30, Avi Kivity wrote:
On 11/14/2010 11:18 AM, Jan Kiszka wrote:
From: Jan Kiszkajan.kis...@siemens.com
Without CONFIG_INTEL_TXT, the user must not enable this feature
in the BIOS. Otherwise, KVM will not work.
Hi,
First of all, if this is not the correct list to send this kind of information
to, please forgive me and i'd be very appreciative if you could let me know the
one i should post this on.
I'm with Scality, developer of an object-based storage software platform,
called Scality RING. A month
I had sent this mail to Michael last week - he agrees that I should
share this information on the list:
On latest net-next-2.6, virtio-net (guest-host) results are:
__
SQ vs MQ (#txqs=8)
# BW1 BW2 (%)
On Mon, Nov 15, 2010 at 09:52:19PM -0500, Kevin O'Connor wrote:
On Mon, Nov 15, 2010 at 03:36:25PM +0200, Gleb Natapov wrote:
On Mon, Nov 15, 2010 at 08:26:35AM -0500, Kevin O'Connor wrote:
On Mon, Nov 15, 2010 at 09:40:08AM +0200, Gleb Natapov wrote:
On Sun, Nov 14, 2010 at 10:40:33PM
86 matches
Mail list logo
