On 07/25/2011 06:04 PM, Markus Armbruster wrote:
Hannes Reineckeh...@suse.de writes:
Markus Armbruster pointed out that not every SCSI command is supported
for a given device type. Based on his patch and suggestiongs this series
cleans up the SCSI device type and adds a check for supported
On 07/25/2011 05:59 PM, Markus Armbruster wrote:
Hannes Reineckeh...@suse.de writes:
Instead of using its own definitions scsi-disk should
be using the device type of the parent device.
Signed-off-by: Hannes Reineckeh...@suse.de
---
hw/scsi-defs.h |6 +-
hw/scsi-disk.c | 48
Hannes Reinecke h...@suse.de writes:
On 07/25/2011 05:59 PM, Markus Armbruster wrote:
Hannes Reineckeh...@suse.de writes:
Instead of using its own definitions scsi-disk should
be using the device type of the parent device.
Signed-off-by: Hannes Reineckeh...@suse.de
---
hw/scsi-defs.h
On 2011-07-26 07:29, André Weidemann wrote:
On 07.07.2011 07:26, André Weidemann wrote:
Hi,
I am running Windows7 x64 in a VM which crashes after starting a certain
game. Actually there are two games both from the same company, that make
the VM crash after starting them.
Windows crashes
On 07/26/2011 08:38 AM, Markus Armbruster wrote:
Hannes Reineckeh...@suse.de writes:
On 07/25/2011 05:59 PM, Markus Armbruster wrote:
Hannes Reineckeh...@suse.de writes:
Instead of using its own definitions scsi-disk should
be using the device type of the parent device.
Signed-off-by:
On 07/26/2011 12:34 AM, Eric Northup wrote:
On Wed, Jul 20, 2011 at 9:50 AM, Avi Kivitya...@redhat.com wrote:
[...]
@@ -130,7 +137,13 @@ static void pc_init1(MemoryRegion *system_memory,
if (pci_enabled) {
pci_bus = i440fx_init(i440fx_state,piix3_devfn, isa_irq,
-
On Tue, Jul 26, 2011 at 6:58 AM, Prateek Sharma prate...@cse.iitb.ac.in wrote:
On Tue, 26 Jul 2011, Stefan Hajnoczi wrote:
On Tue, Jul 26, 2011 at 6:05 AM, Prateek Sharma prate...@cse.iitb.ac.in
wrote:
Hi all,
Is there any equivalent of qemu's virtagent in qemu-kvm?
Welcome to give me your comments, thanks.
Signed-off-by: Zhi Yong Wu wu...@linux.vnet.ibm.com
---
Makefile.objs |2 +-
block.c | 288 +++--
block.h |1 -
block/blk-queue.c | 116 +
The main goal of the patch is to effectively cap the disk I/O speed or counts
of one single VM.It is only one draft, so it unavoidably has some drawbacks, if
you catch them, please let me know.
The patch will mainly introduce one block I/O throttling algorithm, one global
timer and one block
The main goal of the patch is to effectively cap the disk I/O speed or counts
of one single VM.It is only one draft, so it unavoidably has some drawbacks, if
you catch them, please let me know.
The patch will mainly introduce one block I/O throttling algorithm, one global
timer and one block
Welcome to give me your comments, thanks.
Signed-off-by: Zhi Yong Wu wu...@linux.vnet.ibm.com
---
Makefile.objs |2 +-
block.c | 288 +++--
block.h |1 -
block/blk-queue.c | 116 +
On 07/25/2011 09:41 PM, Anthony Liguori wrote:
+/* Initialize a memory region
+ *
+ * The region typically acts as a container for other memory regions.
+ */
I'm also writing a fair bit of documentation right now. We should use
a common format and declare that the doc format in
On 07/25/2011 09:48 PM, Anthony Liguori wrote:
+/* Attempt to simplify a view by merging ajacent ranges */
+static void flatview_simplify(FlatView *view)
+{
+unsigned i;
+FlatRange *r1, *r2;
+
+for (i = 0; i + 1 view-nr; ++i) {
+r1 =view-ranges[i];
+r2
On 07/25/2011 09:56 PM, Anthony Liguori wrote:
On 07/25/2011 09:02 AM, Avi Kivity wrote:
I/O regions will not have ram_addrs, so this is a better name.
Signed-off-by: Avi Kivitya...@redhat.com
Reviewed-by: Anthony Liguori aligu...@us.ibm.com
Although it seems squashable.
Yeah, I'm loath
On Tue, Jul 26, 2011 at 07:29:04AM +0200, André Weidemann wrote:
On 07.07.2011 07:26, André Weidemann wrote:
Hi,
I am running Windows7 x64 in a VM which crashes after starting a certain
game. Actually there are two games both from the same company, that make
the VM crash after starting them.
On 07/25/2011 10:08 PM, Anthony Liguori wrote:
+static void as_memory_ioeventfd_add(AddressSpace *as,
MemoryRegionIoeventfd *fd)
+{
+int r;
+
+if (!fd-match_data || fd-addr.size != 4) {
+abort();
+}
+
+r = kvm_set_ioeventfd_mmio_long(fd-fd, fd-addr.start,
fd-data,
On 07/25/2011 10:12 PM, Anthony Liguori wrote:
On 07/25/2011 09:02 AM, Avi Kivity wrote:
Instead of adding and deleting regions in one pass, do a delete
pass followed by an add pass. This fixes the following case:
from:
0x-0x0fff ram (a1)
0x1000-0x1fff mmio (a2)
0x2000-0x2fff
On 07/25/2011 10:15 PM, Anthony Liguori wrote:
+Region names
+
+
+Regions are assigned names by the constructor. For most regions
these are
+only used for debugging purposes, but RAM regions also use the name
to identify
+live migration sections. This means that RAM region names
On Mon, Jul 25, 2011 at 04:42:50PM -0400, Don Dutile wrote:
On 07/25/2011 04:20 PM, Alex Williamson wrote:
On Mon, 2011-07-25 at 15:37 -0400, Don Dutile wrote:
On 07/24/2011 06:58 AM, Michael S. Tsirkin wrote:
On Sun, Jul 24, 2011 at 11:41:10AM +0300, Michael S. Tsirkin wrote:
On Sun, Jul 24,
On 07/25/2011 10:16 PM, Anthony Liguori wrote:
On 07/25/2011 09:02 AM, Avi Kivity wrote:
Allow changes to the memory hierarchy to be accumulated and
made visible all at once. This reduces computational effort,
especially when an accelerator (e.g. kvm) is involved.
Useful when a single
On 07/25/2011 10:17 PM, Anthony Liguori wrote:
+static void memory_map_init(void)
+{
+system_memory = qemu_malloc(sizeof(*system_memory));
+memory_region_init(system_memory, system, UINT64_MAX);
Would be nice to #define MEM_REG_SIZE_ALL UINT64_MAX
Without reading the docs, it seems
Hi,
On 26.07.2011 12:08, Gleb Natapov wrote:
On Tue, Jul 26, 2011 at 07:29:04AM +0200, André Weidemann wrote:
On 07.07.2011 07:26, André Weidemann wrote:
Hi,
I am running Windows7 x64 in a VM which crashes after starting a certain
game. Actually there are two games both from the same company,
On 07/25/2011 10:20 PM, Anthony Liguori wrote:
On 07/25/2011 09:02 AM, Avi Kivity wrote:
The I/O port space is byte addressable, even for word and long accesses.
An example is the VMware svga card, which has long ports on offsets 0,
1, and 2.
Signed-off-by: Avi Kivitya...@redhat.com
I've
On 07/25/2011 11:02 PM, Anthony Liguori wrote:
On 07/25/2011 09:03 AM, Avi Kivity wrote:
Signed-off-by: Avi Kivitya...@redhat.com
What's the rationale here?
Removing globals and making dependencies explicit.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe
On 07/25/2011 11:20 PM, Anthony Liguori wrote:
On 07/25/2011 09:03 AM, Avi Kivity wrote:
Allow registering a BAR using a MemoryRegion. Once all users are
converted,
pci_register_bar() and pci_register_bar_simple() will be removed.
Signed-off-by: Avi Kivitya...@redhat.com
diff --git
On Tue, Jul 26, 2011 at 12:30 AM, Juan Quintela quint...@redhat.com wrote:
Please send in any agenda items you are interested in covering.
0.15.0 release candidate testing
* http://wiki.qemu.org/Planning/0.15/Testing
* Please test hosts, targets, subsystems, or features you care about!
* May
On 07/22/2011 09:58 PM, Umesh Deshapnde wrote:
-qemu_mod_timer(s-timer, qemu_get_clock_ms(rt_clock) + 100);
+qemu_mod_timer(s-timer, qemu_get_clock_ms(migration_clock) + 100);
if (s-freeze_output)
return;
@@ -246,8 +246,10 @@ static void buffered_rate_tick(void *opaque)
Too keep shadow page consistency, we should write-protect the guest page if
if it is a page structure. Unfortunately, even if the guest page structure is
tear-down and is used for other usage, we still write-protect it and cause page
fault if it is written, in this case, we need to zap the
kvm_mmu_pte_write is unsafe since we need to alloc pte_list_desc in the
function when spte is prefetched, unfortunately, we can not know how many
spte need to be prefetched on this path, that means we can use out of the
free pte_list_desc object in the cache, and BUG_ON() is triggered, also some
Remove the same code between emulator_pio_in_emulated and
emulator_pio_out_emulated
Signed-off-by: Xiao Guangrong xiaoguangr...@cn.fujitsu.com
---
arch/x86/kvm/x86.c | 59 ++-
1 files changed, 26 insertions(+), 33 deletions(-)
diff --git
We usually use repeat string instructions to clear the page, for example,
we call memset to clear a page table, stosb is used in this function, and
repeated for 1024 times, that means we should occupy mmu lock for 1024 times
and walking shadow page cache for 1024 times, it is terrible
In fact,
In current code, the accessed bit is always set when page fault occurred,
do not need to set it on pte write path
Signed-off-by: Xiao Guangrong xiaoguangr...@cn.fujitsu.com
---
arch/x86/include/asm/kvm_host.h |1 -
arch/x86/kvm/mmu.c | 22 +-
2 files
This patchset contains the core of the memory API, with one device
(usb-ohci) coverted for reference. The API is currently implemented on
top of the old ram_addr_t/cpu_register_physical_memory() API, but the plan
is to make it standalone later.
The goals of the API are:
- correctness: by
Simple implementations of memory routers, for example the Cirrus VGA memory
banks
or the 440FX PAM registers can generate adjacent memory regions which are
contiguous.
Detect these and merge them; this saves kvm memory slots and shortens lookup
times.
Signed-off-by: Avi Kivity a...@redhat.com
Currently dirty tracking is implemented by passing through
all calls to the underlying cpu_physical_memory_*() calls.
Reviewed-by: Anthony Liguori aligu...@us.ibm.com
Signed-off-by: Avi Kivity a...@redhat.com
---
memory.c | 39 +++
memory.h |1 +
2 files
Signed-off-by: Avi Kivity a...@redhat.com
---
docs/memory.txt | 172 +++
1 files changed, 172 insertions(+), 0 deletions(-)
create mode 100644 docs/memory.txt
diff --git a/docs/memory.txt b/docs/memory.txt
new file mode 100644
index
The memory API separates the attributes of a memory region (its size, how
reads or writes are handled, dirty logging, and coalescing) from where it
is mapped and whether it is enabled. This allows a device to configure
a memory region once, then hand it off to its parent bus to map it according
For non-RAM memory regions, we cannot tell whether this is an I/O region
or an MMIO region. Since the qemu backing registration is different for
the two, we have to defer initialization until we know which address
space we are in.
These shenanigans will be removed once the backing registration
get_system_memory() provides the root of the memory hierarchy.
This interface is intended to be private between memory.c and exec.c.
If this file is included elsewhere, it should be regarded as a bug (or
TODO item). However, it will be temporarily needed for the conversion
to hierarchical memory
Prepare for multiple address space support by abstracting away the details
of registering a memory range with qemu's flat representation into an
AddressSpace object.
Note operations which are memory specific are not abstracted, since they will
never be called on I/O address spaces anyway.
Allow registering I/O ports via the same mechanism as mmio ranges.
Reviewed-by: Anthony Liguori aligu...@us.ibm.com
Signed-off-by: Avi Kivity a...@redhat.com
---
exec-memory.h |3 ++
memory.c | 60 -
memory.h |2 +
3
I/O regions will not have ram_addrs, so this is a better name.
Reviewed-by: Anthony Liguori aligu...@us.ibm.com
Signed-off-by: Avi Kivity a...@redhat.com
---
memory.c | 18 +-
memory.h |2 +-
2 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/memory.c
Allocate the root memory region and initialize it.
Signed-off-by: Avi Kivity a...@redhat.com
---
exec.c | 19 +++
1 files changed, 19 insertions(+), 0 deletions(-)
diff --git a/exec.c b/exec.c
index 2160ded..d51502f 100644
--- a/exec.c
+++ b/exec.c
@@ -33,6 +33,8 @@
#include
As with the rest of the memory API, the caller associates an eventfd
with an address, and the memory API takes care of registering or
unregistering when the address is made visible or invisible to the
guest.
Signed-off-by: Avi Kivity a...@redhat.com
---
memory.c | 224
Allow changes to the memory hierarchy to be accumulated and
made visible all at once. This reduces computational effort,
especially when an accelerator (e.g. kvm) is involved.
Useful when a single register update causes multiple changes
to an address space.
Signed-off-by: Avi Kivity
This eases the transition to the new API.
Reviewed-by: Anthony Liguori aligu...@us.ibm.com
Signed-off-by: Avi Kivity a...@redhat.com
---
memory.c | 10 ++
memory.h | 10 ++
2 files changed, 20 insertions(+), 0 deletions(-)
diff --git a/memory.c b/memory.c
index
Reviewed-by: Anthony Liguori aligu...@us.ibm.com
Signed-off-by: Avi Kivity a...@redhat.com
---
memory.c | 32
memory.h | 17 +
2 files changed, 49 insertions(+), 0 deletions(-)
diff --git a/memory.c b/memory.c
index df0ed0e..5f2c9ef 100644
---
While eventually this should come from the machine initialization function,
take a short cut to avoid converting all machines now.
Reviewed-by: Anthony Liguori aligu...@us.ibm.com
Signed-off-by: Avi Kivity a...@redhat.com
---
hw/pc.c |3 ++-
hw/pc.h |4 +++-
hw/pc_piix.c |8
Allow registering sysbus device memory using a MemoryRegion. Once all users
are converted, sysbus_init_mmio() and sysbus_init_mmio_cb() will be removed.
Reviewed-by: Anthony Liguori aligu...@us.ibm.com
Signed-off-by: Avi Kivity a...@redhat.com
---
hw/sysbus.c | 27 ---
The I/O port space is byte addressable, even for word and long accesses.
An example is the VMware svga card, which has long ports on offsets 0,
1, and 2.
Reviewed-by: Anthony Liguori aligu...@us.ibm.com
Signed-off-by: Avi Kivity a...@redhat.com
---
ioport.c |4 ++--
1 files changed, 2
Signed-off-by: Avi Kivity a...@redhat.com
---
hw/pc_piix.c | 15 ---
1 files changed, 8 insertions(+), 7 deletions(-)
diff --git a/hw/pc_piix.c b/hw/pc_piix.c
index d83854c..f2d0476 100644
--- a/hw/pc_piix.c
+++ b/hw/pc_piix.c
@@ -68,7 +68,8 @@ static void ioapic_init(IsaIrqState
Instead of adding and deleting regions in one pass, do a delete
pass followed by an add pass. This fixes the following case:
from:
0x-0x0fff ram (a1)
0x1000-0x1fff mmio (a2)
0x2000-0x2fff ram (a3)
to:
0x-0x2fff ram (b1)
The single pass algorithm removed a1, added b2, then
Reviewed-by: Anthony Liguori aligu...@us.ibm.com
Signed-off-by: Avi Kivity a...@redhat.com
---
hw/usb-ohci.c | 42 +-
1 files changed, 17 insertions(+), 25 deletions(-)
diff --git a/hw/usb-ohci.c b/hw/usb-ohci.c
index 8491d59..337b250 100644
---
Reviewed-by: Anthony Liguori aligu...@us.ibm.com
Signed-off-by: Avi Kivity a...@redhat.com
---
hw/pc.c | 59 ---
hw/pc.h |1 +
2 files changed, 41 insertions(+), 19 deletions(-)
diff --git a/hw/pc.c b/hw/pc.c
index 369566a..1c9d89a
Allow registering a BAR using a MemoryRegion. Once all users are converted,
pci_register_bar() and pci_register_bar_simple() will be removed.
Reviewed-by: Anthony Liguori aligu...@us.ibm.com
Signed-off-by: Avi Kivity a...@redhat.com
---
hw/pci.c | 47
This is now done sloppily, via get_system_memory(). Eventually callers
will be converted to stop using that.
Reviewed-by: Anthony Liguori aligu...@us.ibm.com
Signed-off-by: Avi Kivity a...@redhat.com
---
hw/apb_pci.c |2 ++
hw/bonito.c|4 +++-
hw/grackle_pci.c |5
Directly Use mmu_page_zap_pte to zap spte in FNAME(invlpg), also remove the
same code between FNAME(invlpg) and FNAME(sync_page)
Signed-off-by: Xiao Guangrong xiaoguangr...@cn.fujitsu.com
---
arch/x86/kvm/mmu.c | 16 ++--
arch/x86/kvm/paging_tmpl.h | 42
Fast prefetch spte for the unsync shadow page on invlpg path
Signed-off-by: Xiao Guangrong xiaoguangr...@cn.fujitsu.com
---
arch/x86/include/asm/kvm_host.h |4 +---
arch/x86/kvm/mmu.c | 38 +++---
arch/x86/kvm/paging_tmpl.h | 23
In kvm_mmu_pte_write, we do not need to alloc shadow page, so calling
kvm_mmu_free_some_pages is really unnecessary
Signed-off-by: Xiao Guangrong xiaoguangr...@cn.fujitsu.com
---
arch/x86/kvm/mmu.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/arch/x86/kvm/mmu.c
kvm_mmu_pte_write is too long, we split it for better readable
Signed-off-by: Xiao Guangrong xiaoguangr...@cn.fujitsu.com
---
arch/x86/kvm/mmu.c | 180
1 files changed, 111 insertions(+), 69 deletions(-)
diff --git a/arch/x86/kvm/mmu.c
If the shadow page has different cpu mode with current vcpu, we do better
remove them since the OS does not changes cpu mode frequently
Signed-off-by: Xiao Guangrong xiaoguangr...@cn.fujitsu.com
---
arch/x86/kvm/mmu.c | 26 +++---
1 files changed, 19 insertions(+), 7
Sometimes, we only modify the last one byte of a pte to update status bit,
for example, clear_bit is used to clear r/w bit in linux kernel and 'andb'
instruction is used in this function, in this case, kvm_mmu_pte_write will
treat it as misaligned access, and the shadow page table is zapped
On 07/25/2011 11:23 PM, Anthony Liguori wrote:
Very nice series.
Despite my lack of exciting over ioeventfd and coalescing, if you fix
the few minor comments, this should be a no brainer to merge.
Thanks; v2 posted.
Note that this patchset has a logical dependency on my [PATCH]
On 07/26/2011 01:26 PM, Avi Kivity wrote:
+while (i view-nr) {
+j = i + 1;
+while (j view-nr
+can_merge(view-ranges[j-1], view-ranges[j])) {
+view-ranges[i].addr.size += view-ranges[j].addr.size;
+++j;
+}
+++i;
if (j
On 07/26/2011 02:36 PM, Paolo Bonzini wrote:
On 07/26/2011 01:26 PM, Avi Kivity wrote:
+while (i view-nr) {
+j = i + 1;
+while (j view-nr
+ can_merge(view-ranges[j-1], view-ranges[j])) {
+view-ranges[i].addr.size += view-ranges[j].addr.size;
+++j;
On 07/26/2011 01:48 PM, Avi Kivity wrote:
On 07/25/2011 10:16 PM, Anthony Liguori wrote:
On 07/25/2011 09:02 AM, Avi Kivity wrote:
Allow changes to the memory hierarchy to be accumulated and
made visible all at once. This reduces computational effort,
especially when an accelerator (e.g. kvm)
On Mon, Jul 25, 2011 at 02:14:28PM -0600, Alex Williamson wrote:
On Sun, 2011-07-24 at 11:36 +0300, Michael S. Tsirkin wrote:
On Thu, Jul 21, 2011 at 11:02:53AM -0600, Alex Williamson wrote:
This is crazy, why would we only test this for PCI_CAP_ID_EXP? If the
test is going to go in
On 07/26/2011 01:38 PM, Avi Kivity wrote:
if (j != i) {
+memmove(view-ranges[i], view-ranges[j],
+(view-nr - j) * sizeof(view-ranges[j]));
+view-nr -= j - i;
+}
}
Seems to work both ways?
Sure, but you're pointlessly memmove-ing memory over itself.
On 07/26/2011 02:51 PM, Paolo Bonzini wrote:
On 07/26/2011 01:38 PM, Avi Kivity wrote:
if (j != i) {
+memmove(view-ranges[i], view-ranges[j],
+(view-nr - j) * sizeof(view-ranges[j]));
+view-nr -= j - i;
+}
}
Seems to work both ways?
Sure, but you're
On Tue, Jul 26, 2011 at 07:26:46PM +0800, Xiao Guangrong wrote:
We usually use repeat string instructions to clear the page, for example,
By we do you mean Linux guest?
we call memset to clear a page table, stosb is used in this function, and
repeated for 1024 times, that means we should
Detecting write-flooding does not work well, when we handle page written, if
the last speculative spte is not accessed, we treat the page is
write-flooding, however, we can speculative spte on many path, such as pte
prefetch, page synced, that means the last speculative spte may be not point
to
Am 22.07.2011 16:51, schrieb Hannes Reinecke:
Not every command is support for any device type. This patch adds
a check for rejecting unsupported commands.
Signed-off-by: Hannes Reinecke h...@suse.de
---
hw/scsi-disk.c | 104
+++-
1
On 07/26/2011 03:07 PM, Kevin Wolf wrote:
Am 22.07.2011 16:51, schrieb Hannes Reinecke:
Not every command is support for any device type. This patch adds
a check for rejecting unsupported commands.
Signed-off-by: Hannes Reineckeh...@suse.de
---
hw/scsi-disk.c | 104
On Fri, Jul 22, 2011 at 04:51:17PM +0200, Hannes Reinecke wrote:
Not every command is support for any device type. This patch adds
a check for rejecting unsupported commands.
Signed-off-by: Hannes Reinecke h...@suse.de
This seems to conflic with Markus' series. But if we want to invest
any
Am 22.07.2011 16:51, schrieb Hannes Reinecke:
Not every command is support for any device type. This patch adds
a check for rejecting unsupported commands.
Signed-off-by: Hannes Reinecke h...@suse.de
We do emulate SEEK (6), but it's not in your scsi_cmd_table at all.
---
hw/scsi-disk.c |
Am 22.07.2011 16:51, schrieb Hannes Reinecke:
Markus Armbruster pointed out that not every SCSI command is supported
for a given device type. Based on his patch and suggestiongs this series
cleans up the SCSI device type and adds a check for supported commands.
Hannes Reinecke (6):
On 07/26/2011 03:27 PM, Gleb Natapov wrote:
On Tue, Jul 26, 2011 at 07:26:46PM +0800, Xiao Guangrong wrote:
We usually use repeat string instructions to clear the page, for example,
By we do you mean Linux guest?
we call memset to clear a page table, stosb is used in this function, and
On 07/26/2011 03:24 AM, Stefan Hajnoczi wrote:
On Tue, Jul 26, 2011 at 6:58 AM, Prateek Sharmaprate...@cse.iitb.ac.in wrote:
On Tue, 26 Jul 2011, Stefan Hajnoczi wrote:
On Tue, Jul 26, 2011 at 6:05 AM, Prateek Sharmaprate...@cse.iitb.ac.in
wrote:
Hi all,
Is there any equivalent of
On 07/26/2011 03:46 PM, Kevin Wolf wrote:
Am 22.07.2011 16:51, schrieb Hannes Reinecke:
Not every command is support for any device type. This patch adds
a check for rejecting unsupported commands.
Signed-off-by: Hannes Reineckeh...@suse.de
We do emulate SEEK (6), but it's not in your
On 07/26/2011 04:36 AM, Paolo Bonzini wrote:
On 07/26/2011 01:26 PM, Avi Kivity wrote:
+while (i view-nr) {
+j = i + 1;
+while (j view-nr
+can_merge(view-ranges[j-1], view-ranges[j])) {
+view-ranges[i].addr.size += view-ranges[j].addr.size;
On Tue, 2011-07-26 at 14:42 +0300, Michael S. Tsirkin wrote:
On Mon, Jul 25, 2011 at 02:14:28PM -0600, Alex Williamson wrote:
On Sun, 2011-07-24 at 11:36 +0300, Michael S. Tsirkin wrote:
On Thu, Jul 21, 2011 at 11:02:53AM -0600, Alex Williamson wrote:
This is crazy, why would we only
On 07/26/2011 06:41 PM, Richard Henderson wrote:
On 07/26/2011 04:36 AM, Paolo Bonzini wrote:
On 07/26/2011 01:26 PM, Avi Kivity wrote:
+while (i view-nr) {
+j = i + 1;
+while (j view-nr
+ can_merge(view-ranges[j-1],view-ranges[j])) {
+
On Thu, 2011-07-21 at 20:14 +0200, Jan Kiszka wrote:
Update of the unmerged half of this series. It logically depends on
pci: Common overflow prevention, but not mechanically. Changes in this
release only affect the 6th patch. It gained support for 3-byte config
space accesses, received a fix
On 30.10.2010, at 20:54, Vasiliy Kulikov wrote:
Structures kvm_vcpu_events, kvm_debugregs, kvm_pit_state2 and
kvm_clock_data are copied to userland with some padding and reserved
fields unitialized. It leads to leaking of contents of kernel stack
memory. We have to initialize them to zero.
On 07/26/2011 08:05 PM, Alexander Graf wrote:
struct kvm_pit_state2 {
struct kvm_pit_channel_state channels[3];
__u32 flags;
__u32 reserved[9];
};
So memset(ps-reserved) would give you the a __u32 **, no? Same goes for all
the other array sets in here. Or am I
Alexander,
On Tue, Jul 26, 2011 at 19:05 +0200, Alexander Graf wrote:
@@ -2623,6 +2626,7 @@ static void kvm_vcpu_ioctl_x86_get_debugregs(struct
kvm_vcpu *vcpu,
dbgregs-dr6 = vcpu-arch.dr6;
dbgregs-dr7 = vcpu-arch.dr7;
dbgregs-flags = 0;
+ memset(dbgregs-reserved, 0,
On 26.07.2011, at 19:24, Avi Kivity wrote:
On 07/26/2011 08:05 PM, Alexander Graf wrote:
struct kvm_pit_state2 {
struct kvm_pit_channel_state channels[3];
__u32 flags;
__u32 reserved[9];
};
So memset(ps-reserved) would give you the a __u32 **, no? Same goes for
On 26.07.2011, at 19:28, Vasiliy Kulikov wrote:
Alexander,
On Tue, Jul 26, 2011 at 19:05 +0200, Alexander Graf wrote:
@@ -2623,6 +2626,7 @@ static void kvm_vcpu_ioctl_x86_get_debugregs(struct
kvm_vcpu *vcpu,
dbgregs-dr6 = vcpu-arch.dr6;
dbgregs-dr7 = vcpu-arch.dr7;
From: Amos Kong ak...@redhat.com
Uses kernel supported nmi_watchdog to test the nmi support of kvm,
check the nmi count in Linux platform through /proc/interrupts.
Changes from v2:
* Updated the test to use more current KVM autotest API
Signed-off-by: Amos Kong ak...@redhat.com
---
On 07/26/2011 03:25 PM, Lucas Meneghel Rodrigues wrote:
From: Amos Kongak...@redhat.com
Uses kernel supported nmi_watchdog to test the nmi support of kvm,
check the nmi count in Linux platform through /proc/interrupts.
Hi Amos, applied your test, thanks!
Changes from v2:
* Updated the
On Thu, Apr 21, 2011 at 4:33 AM, Amos Kong ak...@redhat.com wrote:
This case is used to test the drift between host and guest.
Use taskset to make tsc program execute in a single cpu.
If the drift ratio bigger than 10%, then fail this case.
Hi Amos, per the last conversation we've had about
On Tue, Jul 26, 2011 at 04:59:06PM +0800, Zhi Yong Wu wrote:
Welcome to give me your comments, thanks.
Signed-off-by: Zhi Yong Wu wu...@linux.vnet.ibm.com
---
Makefile.objs |2 +-
block.c | 288
+++--
block.h |
The bcm5761 provides a PCIe Cap structure (capid=0x10)
that is invalid, providing one that is 8 bytes shorter
than the v2 PCIe spec defines.
This leads to a memory corruption when mapped for device-assigment.
Add a check in assigned_device_pci_cap_init() to correct
this hw error for this device,
On Tue, 2011-07-26 at 18:08 -0400, Donald Dutile wrote:
The bcm5761 provides a PCIe Cap structure (capid=0x10)
that is invalid, providing one that is 8 bytes shorter
than the v2 PCIe spec defines.
This leads to a memory corruption when mapped for device-assigment.
Add a check in
#2312;#2350;#2375;#2354;
#2330;#2375;#2340;#2366;#2357;#2344;#2368;
#2310;#2346;#2325;#2366; #2312; - #2350;#2375;#2354;
#2326;#2366;#2340;#2366;
#2344;#2367;#2359;#2381;#2325;#2381;#2352;#2367;#2351;#2325;#2352;#2339;.
#2325;#2371;#2346;#2351;#2366; #2343;#2381;#2351;#2366;#2344;
On 07/26/2011 08:27 PM, Gleb Natapov wrote:
On Tue, Jul 26, 2011 at 07:26:46PM +0800, Xiao Guangrong wrote:
We usually use repeat string instructions to clear the page, for example,
By we do you mean Linux guest?
I do not know other guests except linux, but, generally rep instruction is
not
On Wed, Jul 27, 2011 at 09:47:52AM +0800, Xiao Guangrong wrote:
On 07/26/2011 08:27 PM, Gleb Natapov wrote:
On Tue, Jul 26, 2011 at 07:26:46PM +0800, Xiao Guangrong wrote:
We usually use repeat string instructions to clear the page, for example,
By we do you mean Linux guest?
I do not
97 matches
Mail list logo
