On Sa, 2013-09-07 at 00:53 -0400, Bandan Das wrote:
Currently, hda-codec mixer emulation can only be enabled by using the
--enable-mixemu option to configure at compile time with the default
value being off. These patches enable making mixer emulation
selectable
at runtime which is more
On 09/09/2013 03:50 PM, Alexander Graf wrote:
Am 09.09.2013 um 04:40 schrieb Alexey Kardashevskiy a...@ozlabs.ru:
On 09/06/2013 01:11 AM, Alexander Graf wrote:
On 05.09.2013, at 16:26, Benjamin Herrenschmidt wrote:
On Thu, 2013-09-05 at 16:14 +0200, Andreas Färber wrote:
Are you
Am 09.09.2013 um 07:58 schrieb Alexey Kardashevskiy a...@ozlabs.ru:
On 09/09/2013 03:50 PM, Alexander Graf wrote:
Am 09.09.2013 um 04:40 schrieb Alexey Kardashevskiy a...@ozlabs.ru:
On 09/06/2013 01:11 AM, Alexander Graf wrote:
On 05.09.2013, at 16:26, Benjamin Herrenschmidt wrote:
Hi folks,
Any comments? ;-P
Wanlong Gao
As you know, QEMU can't direct it's memory allocation now, this may cause
guest cross node access performance regression.
And, the worse thing is that if PCI-passthrough is used,
direct-attached-device uses DMA transfer between device and qemu
On Fri, Sep 06, 2013 at 01:23:32PM +0100, Peter Maydell wrote:
On 6 September 2013 13:19, Jens Freimann jf...@linux.vnet.ibm.com wrote:
Add symbols required for the s390 floating interrupt controller (flic)
Updates to linux-headers should be the result of a sync
against a specified mainline
On Fri, Sep 06, 2013 at 01:32:52PM +0100, Peter Maydell wrote:
On 6 September 2013 13:19, Jens Freimann jf...@linux.vnet.ibm.com wrote:
@@ -839,6 +903,7 @@ struct kvm_device_attr {
#define KVM_DEV_TYPE_FSL_MPIC_20 1
#define KVM_DEV_TYPE_FSL_MPIC_42 2
#define
Il 09/09/2013 05:26, Liu, Jinsong ha scritto:
From 6f40a66521e012170493964a2135fb3b4ae7c9b2 Mon Sep 17 00:00:00 2001
From: Liu Jinsong jinsong@intel.com
Date: Sun, 8 Sep 2013 00:33:19 +0800
Subject: [PATCH V3 1/2] qemu: Adjust qemu wakeup
Currently Xen hvm s3 has a bug coming from the
Hello Richard,
On 02.09.2013 19:54, Richard Henderson wrote:
I'm not sure if I posted v2 or not, but my branch is named -3,
therefore this is v3. ;-)
The jumbo fixme patch from v1 has been split up. This has been
updated for the changes in the tlb helpers over the past few weeks.
For the
The isoc packet path in the ehci code has a bad qobject cast, causing an
abort, this patch fixes this.
Note this problem is backported in 1.6.0 too, and this patch should be
backported to the 1.6.0 stable tree.
Signed-off-by: Hans de Goede hdego...@redhat.com
---
hw/usb/hcd-ehci.c | 3 ++-
1
We'll need a pointer to the actual pci/sysbus device,
stick a pointer to it into the EHCIState struct.
https://bugzilla.redhat.com/show_bug.cgi?id=1005495
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
hw/usb/hcd-ehci.c | 3 ++-
hw/usb/hcd-ehci.h | 1 +
2 files changed, 3 insertions(+), 1
Il 08/09/2013 13:40, Gleb Natapov ha scritto:
On Thu, Sep 05, 2013 at 03:06:21PM +0200, Paolo Bonzini wrote:
On KVM, the KVM_SET_XSAVE would be executed with a 0 xstate_bv,
and not restore anything.
XRSTOR restores FP/SSE state to reset state if no bits are set in
xstate_bv. This is what
Am 09.09.2013 um 03:57 hat xuanmao_001 geschrieben:
the other question: when I change the buffer size #define IO_BUF_SIZE 32768
to #define IO_BUF_SIZE (1 * 1024 * 1024), the savevm is more quickly.
Is this for cache=unsafe as well?
Juan, any specific reason for using 32k? I think it
I sent patches that should eliminate the difference between the first
and second snapshot at least.
where I can find the patches that can eliminate the difference between the first
and second snapshot ? Does they fit qemu-kvm-1.0,1 ?
xuanmao_001
From: Kevin Wolf
Date: 2013-09-09 16:35
To:
Il 08/09/2013 13:52, Gleb Natapov ha scritto:
On Thu, Sep 05, 2013 at 03:06:22PM +0200, Paolo Bonzini wrote:
QEMU moves state from CPUArchState to struct kvm_xsave and back when it
invokes the KVM_*_XSAVE ioctls. Because it doesn't treat the XSAVE
region as an opaque blob, it might be
On Mon, Sep 09, 2013 at 10:31:15AM +0200, Paolo Bonzini wrote:
Il 08/09/2013 13:40, Gleb Natapov ha scritto:
On Thu, Sep 05, 2013 at 03:06:21PM +0200, Paolo Bonzini wrote:
On KVM, the KVM_SET_XSAVE would be executed with a 0 xstate_bv,
and not restore anything.
XRSTOR restores FP/SSE
Hi,
On 09/09/2013 10:20 AM, Gerd Hoffmann wrote:
We'll need a pointer to the actual pci/sysbus device,
stick a pointer to it into the EHCIState struct.
https://bugzilla.redhat.com/show_bug.cgi?id=1005495
Looks like we've been working on exactly the same bug at the
same time, but we've come
Am 09.09.2013 um 10:47 hat xuanmao_001 geschrieben:
I sent patches that should eliminate the difference between the first
and second snapshot at least.
where I can find the patches that can
eliminate the difference between the first
and second snapshot ? Does they fit qemu-kvm-1.0,1 ?
I
On Mon, Sep 09, 2013 at 10:51:58AM +0200, Paolo Bonzini wrote:
Il 08/09/2013 13:52, Gleb Natapov ha scritto:
On Thu, Sep 05, 2013 at 03:06:22PM +0200, Paolo Bonzini wrote:
QEMU moves state from CPUArchState to struct kvm_xsave and back when it
invokes the KVM_*_XSAVE ioctls. Because it
On 09.09.2013, at 11:29, Benjamin Herrenschmidt wrote:
On Mon, 2013-09-09 at 08:06 +0200, Alexander Graf wrote:
I think it's ok to restrict live migration to machines with the same
tb frequency when kvm is enabled. Whether you implement it through a
hardcoded 512Mhz or through a timebase
Am 09.09.2013 um 11:14 hat Tal Kain geschrieben:
It is a valid case that the read data's size is smaller than the
requested size since there could be files that are smaller than
the minimum block size (For ex. when a VMDK disk descriptor file)
Signed-off-by: Tal Kain
On Mon, 2013-09-09 at 08:06 +0200, Alexander Graf wrote:
I think it's ok to restrict live migration to machines with the same
tb frequency when kvm is enabled. Whether you implement it through a
hardcoded 512Mhz or through a timebase value that gets live migrated
and then compared is up to you
On Mon, 2013-09-09 at 11:32 +0200, Alexander Graf wrote:
On 09.09.2013, at 11:29, Benjamin Herrenschmidt wrote:
On Mon, 2013-09-09 at 08:06 +0200, Alexander Graf wrote:
I think it's ok to restrict live migration to machines with the same
tb frequency when kvm is enabled. Whether you
On 09.09.2013, at 11:38, Benjamin Herrenschmidt wrote:
On Mon, 2013-09-09 at 11:32 +0200, Alexander Graf wrote:
On 09.09.2013, at 11:29, Benjamin Herrenschmidt wrote:
On Mon, 2013-09-09 at 08:06 +0200, Alexander Graf wrote:
I think it's ok to restrict live migration to machines with the
Hi Will,
Just trying to understand the scope of platform device assignment to guest on
ARM. So, are the AMBA devices also represented in the device tree?
Regards
Varun
-Original Message-
From: kvm-ppc-ow...@vger.kernel.org [mailto:kvm-ppc-
ow...@vger.kernel.org] On Behalf Of Will
Il 09/09/2013 11:18, Gleb Natapov ha scritto:
On Mon, Sep 09, 2013 at 10:51:58AM +0200, Paolo Bonzini wrote:
Il 08/09/2013 13:52, Gleb Natapov ha scritto:
On Thu, Sep 05, 2013 at 03:06:22PM +0200, Paolo Bonzini wrote:
QEMU moves state from CPUArchState to struct kvm_xsave and back when it
Il 09/09/2013 11:03, Gleb Natapov ha scritto:
On Mon, Sep 09, 2013 at 10:31:15AM +0200, Paolo Bonzini wrote:
Il 08/09/2013 13:40, Gleb Natapov ha scritto:
On Thu, Sep 05, 2013 at 03:06:21PM +0200, Paolo Bonzini wrote:
On KVM, the KVM_SET_XSAVE would be executed with a 0 xstate_bv,
and not
We'll need a pointer to the actual pci/sysbus device,
stick a pointer to it into the EHCIState struct.
https://bugzilla.redhat.com/show_bug.cgi?id=1005495
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
hw/usb/hcd-ehci.c | 7 +++
hw/usb/hcd-ehci.h | 1 +
2 files changed, 4 insertions(+),
On Mo, 2013-09-09 at 11:04 +0200, Hans de Goede wrote:
Hi,
On 09/09/2013 10:20 AM, Gerd Hoffmann wrote:
We'll need a pointer to the actual pci/sysbus device,
stick a pointer to it into the EHCIState struct.
https://bugzilla.redhat.com/show_bug.cgi?id=1005495
Looks like we've been
Il 09/09/2013 10:20, Hans de Goede ha scritto:
The isoc packet path in the ehci code has a bad qobject cast, causing an
abort, this patch fixes this.
Note this problem is backported in 1.6.0 too, and this patch should be
backported to the 1.6.0 stable tree.
Signed-off-by: Hans de Goede
When amending the size option for a qcow2 image, use bdrv_truncate
instead of qcow2_truncate directly, since the latter will not adjust the
total_sectors count in the BDS structure (whereas the former will).
Signed-off-by: Max Reitz mre...@redhat.com
---
Depends on (follow-up to):
- block/qcow2:
Il 06/09/2013 20:41, Eduardo Otubo ha scritto:
Hello,
Any chance to get this patch applied?
Thanks!
Paul, perhaps you can add yourself to MAINTAINERS and send a pull request?
Paolo
On 09/04/2013 11:11 AM, Paul Moore wrote:
On Wednesday, September 04, 2013 09:25:08 AM Eduardo Otubo
Ping!
thanks
-- PMM
On 25 August 2013 15:59, Peter Maydell peter.mayd...@linaro.org wrote:
The bswap.h header includes a set of legacy unaligned functions
that (since commit c732a52d3 at the beginning of this year) are
just wrappers for underlying {ld,st}type functions. The legacy
functions
Il 09/09/2013 03:34, Fam Zheng ha scritto:
On Fri, 09/06 20:19, Lluís Vilanova wrote:
Fam Zheng writes:
[...]
Because $(obj) here is './block', instead of '../block'. This doesn't
hurt compiling because we basically build all .o from top Makefile,
before entering Makefile.target, but it will
On Mon, Sep 09, 2013 at 11:50:03AM +0200, Paolo Bonzini wrote:
Il 09/09/2013 11:18, Gleb Natapov ha scritto:
On Mon, Sep 09, 2013 at 10:51:58AM +0200, Paolo Bonzini wrote:
Il 08/09/2013 13:52, Gleb Natapov ha scritto:
On Thu, Sep 05, 2013 at 03:06:22PM +0200, Paolo Bonzini wrote:
QEMU
Il 09/09/2013 04:26, Fam Zheng ha scritto:
Actually I would like a try to keep $i-{obj,cflags,libs}:
foo-obj := bar.o biz.o
foo-libs := $(FOO_LIBS)
foo-cflags := $(FOO_CFLAGS)
getting rid of all the $(obj)/'s and expand them in the toplevel unnest magic
(because we know
On 6 September 2013 18:19, Lluís Vilanova vilan...@ac.upc.edu wrote:
Fam Zheng writes:
[...]
Because $(obj) here is './block', instead of '../block'. This doesn't
hurt compiling because we basically build all .o from top Makefile,
before entering Makefile.target, but it will affact arriving
Hi,
On 09/09/2013 11:57 AM, Gerd Hoffmann wrote:
We'll need a pointer to the actual pci/sysbus device,
stick a pointer to it into the EHCIState struct.
https://bugzilla.redhat.com/show_bug.cgi?id=1005495
Looks good, note you've forgotten to add qemu-stable,
I've done so now.
Acked-by: Hans
This patch implements the NetClientInfo.receive_iov method for the
e1000 device emulation. In this way a network backend that uses
qemu_sendv_packet() can deliver the fragmented packet without
requiring an additional copy in the frontend/backend network code
(nc_sendv_compat() function).
The
On Mon, Sep 09, 2013 at 11:53:45AM +0200, Paolo Bonzini wrote:
Il 09/09/2013 11:03, Gleb Natapov ha scritto:
On Mon, Sep 09, 2013 at 10:31:15AM +0200, Paolo Bonzini wrote:
Il 08/09/2013 13:40, Gleb Natapov ha scritto:
On Thu, Sep 05, 2013 at 03:06:21PM +0200, Paolo Bonzini wrote:
On KVM,
On Mon, Sep 09, 2013 at 01:54:50PM +0300, Gleb Natapov wrote:
On Mon, Sep 09, 2013 at 11:53:45AM +0200, Paolo Bonzini wrote:
Il 09/09/2013 11:03, Gleb Natapov ha scritto:
On Mon, Sep 09, 2013 at 10:31:15AM +0200, Paolo Bonzini wrote:
Il 08/09/2013 13:40, Gleb Natapov ha scritto:
On
Il 09/09/2013 12:54, Gleb Natapov ha scritto:
On Mon, Sep 09, 2013 at 11:53:45AM +0200, Paolo Bonzini wrote:
Il 09/09/2013 11:03, Gleb Natapov ha scritto:
On Mon, Sep 09, 2013 at 10:31:15AM +0200, Paolo Bonzini wrote:
Il 08/09/2013 13:40, Gleb Natapov ha scritto:
On Thu, Sep 05, 2013 at
On Thu, 5 Sep 2013, Fabio Fantoni wrote:
Il 05/09/2013 16:04, Stefano Stabellini ha scritto:
On Thu, 5 Sep 2013, Fabio Fantoni wrote:
About qemu default empty and unusable floppy and cdrom I have already
reply at
start of year that qemu traditional does not have them.
The
Note: The series is incomplete, for review only
PCI spec requires that a transaction that has not been claimed
by any PCI bus devices will be terminated by the initiator
with master abort. For read transactions -1() is returned and
writes are silently dropped.
The series deals also with
Priority is used to make visible some subregions by obscuring
the parent MemoryRegion addresses overlapping with the subregion.
By allowing the priority to be negative the opposite can be done:
Allow a subregion to be visible on all the addresses not covered
by the parent MemoryRegion or other
Created a MemoryRegion with negative priority that
spans over all the pci address space.
It intercepts the accesses to unassigned pci
address space and will follow the pci spec:
1. returns -1 on read
2. does nothing on write
3. sets the RECEIVED MASTER ABORT bit in the STATUS register
of
Note: The series is incomplete, for review only
PCI spec requires that a transaction that has not been claimed
by any PCI bus devices will be terminated by the initiator
with master abort. For read transactions -1() is returned and
writes are silently dropped.
The series deals also with
Priority is used to make visible some subregions by obscuring
the parent MemoryRegion addresses overlapping with the subregion.
By allowing the priority to be negative the opposite can be done:
Allow a subregion to be visible on all the addresses not covered
by the parent MemoryRegion or other
Created a MemoryRegion with negative priority that
spans over all the pci address space.
It intercepts the accesses to unassigned pci
address space and will follow the pci spec:
1. returns -1 on read
2. does nothing on write
3. sets the RECEIVED MASTER ABORT bit in the STATUS register
of
On Mon, Sep 09, 2013 at 01:07:37PM +0200, Paolo Bonzini wrote:
In fact, another bug is that kvm_vcpu_ioctl_x86_set_xsave ignores
xstate_bv when XSAVE is not available. Instead, it should reset the
FXSAVE data to processor-reset values (except for MXCSR which always
comes from XRSTOR
On 9 September 2013 12:11, Marcel Apfelbaum marce...@redhat.com wrote:
Priority is used to make visible some subregions by obscuring
the parent MemoryRegion addresses overlapping with the subregion.
By allowing the priority to be negative the opposite can be done:
Allow a subregion to be
On Mon, Sep 09, 2013 at 02:11:54PM +0300, Marcel Apfelbaum wrote:
Created a MemoryRegion with negative priority that
spans over all the pci address space.
It intercepts the accesses to unassigned pci
address space and will follow the pci spec:
1. returns -1 on read
2. does nothing on write
On Mon, Sep 09, 2013 at 02:21:35PM +0300, Marcel Apfelbaum wrote:
Priority is used to make visible some subregions by obscuring
the parent MemoryRegion addresses overlapping with the subregion.
By allowing the priority to be negative the opposite can be done:
Allow a subregion to be visible
On Mon, Sep 09, 2013 at 12:02:57AM -0500, Yaodong Yang wrote:
1. I create a raw image named as win8.img, using the following command:
/usr/local/kvm/bin/qemu-img create -f raw win8.img 20G
2. I try to install win8 with the following command, but I failed several
times.
sudo
On 9 September 2013 12:41, Michael S. Tsirkin m...@redhat.com wrote:
On Mon, Sep 09, 2013 at 02:21:35PM +0300, Marcel Apfelbaum wrote:
Priority is used to make visible some subregions by obscuring
the parent MemoryRegion addresses overlapping with the subregion.
By allowing the priority to be
On Mon, Sep 09, 2013 at 12:45:12PM +0100, Peter Maydell wrote:
On 9 September 2013 12:41, Michael S. Tsirkin m...@redhat.com wrote:
On Mon, Sep 09, 2013 at 02:21:35PM +0300, Marcel Apfelbaum wrote:
Priority is used to make visible some subregions by obscuring
the parent MemoryRegion
Il 09/09/2013 13:28, Gleb Natapov ha scritto:
On an XSAVE host, when the guest FPU state is loaded KVM will do an
XRSTOR. The XRSTOR will restore the FPU state to default values.
On a non-XSAVE host, when the guest FPU state is loaded KVM will do an
FXRSTR. The FXRSTR will load the FPU
On Mon, Sep 09, 2013 at 02:48:55PM +0300, Michael S. Tsirkin wrote:
On Mon, Sep 09, 2013 at 12:45:12PM +0100, Peter Maydell wrote:
On 9 September 2013 12:41, Michael S. Tsirkin m...@redhat.com wrote:
On Mon, Sep 09, 2013 at 02:21:35PM +0300, Marcel Apfelbaum wrote:
Priority is used to
On Sun, Aug 25, 2013 at 03:59:28PM +0100, Peter Maydell wrote:
The bswap.h header includes a set of legacy unaligned functions
that (since commit c732a52d3 at the beginning of this year) are
just wrappers for underlying {ld,st}type functions. The legacy
functions aren't used in many places, so
On Fri, Sep 06, 2013 at 11:24:31AM +0800, Wenchao Xia wrote:
This series add test case for fd passing with unix socket at runtime. Since
getfd and closefd interface will interact with monitor's data, so it will
help to do regression test for monitor patches. Since python2 do not support
Il 09/09/2013 12:41, Gleb Natapov ha scritto:
In fact, perhaps even XSTATE_SUPPORTED is not restrictive enough here,
and we should hide all features that are not visible in CPUID. It is
okay, however, to test it in cpu_post_load.
The kernel should not even return state that is not visible in
On Mon, Sep 09, 2013 at 01:46:49PM +0200, Paolo Bonzini wrote:
Yes. QEMU unmarshals information from the XSAVE region and back, so it
cannot support MPX or AVX-512 yet (even if KVM were). Separate bug,
though.
IMO this is the main issue here, not separate bug. If we gonna let guest
On Wed, Sep 04, 2013 at 07:08:51PM +0200, Sebastian Ottlik wrote:
diff --git a/util/oslib-posix.c b/util/oslib-posix.c
index 3dc8b1b..f071793 100644
--- a/util/oslib-posix.c
+++ b/util/oslib-posix.c
@@ -159,6 +159,20 @@ void qemu_set_nonblock(int fd)
fcntl(fd, F_SETFL, f | O_NONBLOCK);
Am 03.09.2013 um 10:09 hat Max Reitz geschrieben:
This series adds support to qemu-img, block and qcow2 for amending image
options on existing image files.
Depends on:
- option: Add assigned flag to QEMUOptionParameter
- qcow2-refcount: Snapshot update for zero clusters (series, v3)
-
On Mon, 2013-09-09 at 12:28 +0100, Peter Maydell wrote:
On 9 September 2013 12:11, Marcel Apfelbaum marce...@redhat.com wrote:
Priority is used to make visible some subregions by obscuring
the parent MemoryRegion addresses overlapping with the subregion.
By allowing the priority to be
On Thu, Sep 05, 2013 at 03:48:16PM +0200, Sebastian Ottlik wrote:
On 04.09.2013 19:08, Sebastian Ottlik wrote:
This patchset disabels all use of SO_REUSEADDR on Windows. On Windows systems
the default behaviour is equivalent to SO_REUSEADDR on other operating
systems. SO_REUSEADDR can still be
On Wed, Sep 04, 2013 at 08:26:25PM +1000, Alexey Kardashevskiy wrote:
KVM request types are normally defined using hex constants but QEMU traces
print decimal values instead, which is not very convenient.
This changes the request type format from %d to %x.
Signed-off-by: Alexey
On Mon, 2013-09-09 at 14:40 +0300, Michael S. Tsirkin wrote:
On Mon, Sep 09, 2013 at 02:11:54PM +0300, Marcel Apfelbaum wrote:
Created a MemoryRegion with negative priority that
spans over all the pci address space.
It intercepts the accesses to unassigned pci
address space and will
On 09.09.2013 14:05, Stefan Hajnoczi wrote:
On Thu, Sep 05, 2013 at 03:48:16PM +0200, Sebastian Ottlik wrote:
On 04.09.2013 19:08, Sebastian Ottlik wrote:
This patchset disabels all use of SO_REUSEADDR on Windows. On Windows systems
the default behaviour is equivalent to SO_REUSEADDR on other
On Mon, 2013-09-02 at 15:38 +0100, Peter Maydell wrote:
On 2 September 2013 15:13, Marcel Apfelbaum marce...@redhat.com wrote:
Priority is used to make visible some subregions by obscuring
the parent MemoryRegion addresses overlapping with the subregion.
By allowing the priority to be
On 9 September 2013 12:54, Michael S. Tsirkin m...@redhat.com wrote:
On Sun, Aug 25, 2013 at 03:59:28PM +0100, Peter Maydell wrote:
The bswap.h header includes a set of legacy unaligned functions
that (since commit c732a52d3 at the beginning of this year) are
just wrappers for underlying
On Mon, Sep 09, 2013 at 03:11:55PM +0300, Marcel Apfelbaum wrote:
On Mon, 2013-09-09 at 14:40 +0300, Michael S. Tsirkin wrote:
On Mon, Sep 09, 2013 at 02:11:54PM +0300, Marcel Apfelbaum wrote:
Created a MemoryRegion with negative priority that
spans over all the pci address space.
It
On Monday, September 09, 2013 12:38:12 PM Paolo Bonzini wrote:
Il 06/09/2013 20:41, Eduardo Otubo ha scritto:
Hello,
Any chance to get this patch applied?
Thanks!
Paul, perhaps you can add yourself to MAINTAINERS and send a pull request?
Paolo
Out of respect for the work
On Mon, 2013-09-09 at 15:23 +0300, Michael S. Tsirkin wrote:
On Mon, Sep 09, 2013 at 03:11:55PM +0300, Marcel Apfelbaum wrote:
On Mon, 2013-09-09 at 14:40 +0300, Michael S. Tsirkin wrote:
On Mon, Sep 09, 2013 at 02:11:54PM +0300, Marcel Apfelbaum wrote:
Created a MemoryRegion with
Follow-up to Rusty's virtio endianness serie: enough to get a working
virtfs mount.
Note that st*_raw and ld*_raw are effectively replaced by st*_p and ld*_p.
Signed-off-by: Greg Kurz gk...@linux.vnet.ibm.com
---
hw/9pfs/virtio-9p-device.c |3 ++-
1 file changed, 2 insertions(+), 1
On 9 September 2013 13:43, Marcel Apfelbaum marce...@redhat.com wrote:
The scenario is covered only for the primary bus and not for buses
behind the PCI bridge (the later being handled differently.)
In this case, isn't the Host Bridge always device 00.0?
No. For instance the host controller
On Mon, Sep 09, 2013 at 01:52:11PM +0100, Peter Maydell wrote:
On 9 September 2013 13:43, Marcel Apfelbaum marce...@redhat.com wrote:
The scenario is covered only for the primary bus and not for buses
behind the PCI bridge (the later being handled differently.)
In this case, isn't the Host
On 9 September 2013 13:59, Michael S. Tsirkin m...@redhat.com wrote:
On Mon, Sep 09, 2013 at 01:52:11PM +0100, Peter Maydell wrote:
It would be conceptually nicer not to treat host bridges as
a special case but instead to just report the abort back
to whatever the PCI master was (which might
On Mon, 2013-09-09 at 13:52 +0100, Peter Maydell wrote:
On 9 September 2013 13:43, Marcel Apfelbaum marce...@redhat.com wrote:
The scenario is covered only for the primary bus and not for buses
behind the PCI bridge (the later being handled differently.)
In this case, isn't the Host Bridge
On 09/06/2013 01:20 AM, Gerd Hoffmann wrote:
The local spice renderer assumes the primary surface is located at the
start of the ram bar. This used to be a requirement in qxl hardware
revision 1. In revision 2+ this is relaxed. Nevertheless guest drivers
continued to use the traditional
On Mon, 2013-09-09 at 14:02 +0100, Peter Maydell wrote:
On 9 September 2013 13:59, Michael S. Tsirkin m...@redhat.com wrote:
On Mon, Sep 09, 2013 at 01:52:11PM +0100, Peter Maydell wrote:
It would be conceptually nicer not to treat host bridges as
a special case but instead to just report
On 9 September 2013 14:07, Marcel Apfelbaum marce...@redhat.com wrote:
This is exactly my point. ALL device on the bus can be masters
of a DMA transaction. So adding an interface as suggested by
Michael: pci_set_master_for_master_abort(PCIBus *, PCIDevice *)
for the general case (a device
On 9 September 2013 14:15, Marcel Apfelbaum marce...@redhat.com wrote:
On Mon, 2013-09-09 at 14:02 +0100, Peter Maydell wrote:
Can you just pick the device which is (a subclass of)
TYPE_PCI_HOST_BRIDGE, or do we have host bridges which
aren't using that class?
This is what I would really want
On 09/09/2013 09:36 AM, Paul Moore wrote:
On Monday, September 09, 2013 12:38:12 PM Paolo Bonzini wrote:
Il 06/09/2013 20:41, Eduardo Otubo ha scritto:
Hello,
Any chance to get this patch applied?
Thanks!
Paul, perhaps you can add yourself to MAINTAINERS and send a pull request?
On Mon, 2013-09-09 at 14:19 +0100, Peter Maydell wrote:
On 9 September 2013 14:15, Marcel Apfelbaum marce...@redhat.com wrote:
On Mon, 2013-09-09 at 14:02 +0100, Peter Maydell wrote:
Can you just pick the device which is (a subclass of)
TYPE_PCI_HOST_BRIDGE, or do we have host bridges which
On 9 September 2013 14:29, Marcel Apfelbaum marce...@redhat.com wrote:
My issue is that we have at least 2 ways to model the bridges:
1. TYPE_PCI_HOST_BRIDGE
* derives from TYPE_SYS_BUS_DEVICE
* has a bus
* one of the bus devices is a TYPE_I440FX_PCI_DEVICE which
derives from
On Mon, 2013-09-09 at 14:16 +0100, Peter Maydell wrote:
On 9 September 2013 14:07, Marcel Apfelbaum marce...@redhat.com wrote:
This is exactly my point. ALL device on the bus can be masters
of a DMA transaction. So adding an interface as suggested by
Michael:
Il 09/09/2013 15:20, Eduardo Otubo ha scritto:
Out of respect for the work that Eduardo has done, and is
continuing to do, with the QEMU seccomp filtering, I think Eduardo
should be the one to take on this role. If Eduardo declines I'll do
ahead and submit a patch adding myself to the
Add a configure switch which enables an error propagation backtrace.
This results in the error_set function prepending every message by the
source file name, function and line in which it was called, as well as
error_propagate appending this information to the propagated message,
resulting in a
On Mon, 2013-09-09 at 03:29 +, Liu, Jinsong wrote:
From 18344216b432648605726b137b348f28ef64a4ef Mon Sep 17 00:00:00 2001
From: Liu Jinsong jinsong@intel.com
Date: Fri, 23 Aug 2013 23:30:23 +0800
Subject: [PATCH V3] xl: HVM domain S3 bugfix
Currently Xen hvm s3 has a bug coming from
On Mon, Sep 09, 2013 at 03:43:49PM +0300, Marcel Apfelbaum wrote:
On Mon, 2013-09-09 at 15:23 +0300, Michael S. Tsirkin wrote:
On Mon, Sep 09, 2013 at 03:11:55PM +0300, Marcel Apfelbaum wrote:
On Mon, 2013-09-09 at 14:40 +0300, Michael S. Tsirkin wrote:
On Mon, Sep 09, 2013 at 02:11:54PM
On Mon, Sep 09, 2013 at 02:02:47PM +0100, Peter Maydell wrote:
On 9 September 2013 13:59, Michael S. Tsirkin m...@redhat.com wrote:
On Mon, Sep 09, 2013 at 01:52:11PM +0100, Peter Maydell wrote:
It would be conceptually nicer not to treat host bridges as
a special case but instead to just
On Mon, Sep 09, 2013 at 04:07:53PM +0300, Marcel Apfelbaum wrote:
On Mon, 2013-09-09 at 13:52 +0100, Peter Maydell wrote:
On 9 September 2013 13:43, Marcel Apfelbaum marce...@redhat.com wrote:
The scenario is covered only for the primary bus and not for buses
behind the PCI bridge (the
Hi,
On Mon, Aug 26, 2013 at 01:26:11PM -0700, Richard Henderson wrote:
Ping.
Sorry for the delay, adding it to the next pull request.
Riku
On 08/16/2013 11:24 PM, Richard Henderson wrote:
Ping.
r~
On 07/24/2013 12:50 PM, Richard Henderson wrote:
It has been pointed out on
On Mon, 2013-09-09 at 14:39 +0100, Peter Maydell wrote:
On 9 September 2013 14:29, Marcel Apfelbaum marce...@redhat.com wrote:
My issue is that we have at least 2 ways to model the bridges:
1. TYPE_PCI_HOST_BRIDGE
* derives from TYPE_SYS_BUS_DEVICE
* has a bus
* one of the bus
On Mon, Sep 09, 2013 at 04:29:04PM +0300, Marcel Apfelbaum wrote:
On Mon, 2013-09-09 at 14:19 +0100, Peter Maydell wrote:
On 9 September 2013 14:15, Marcel Apfelbaum marce...@redhat.com wrote:
On Mon, 2013-09-09 at 14:02 +0100, Peter Maydell wrote:
Can you just pick the device which is (a
On Fri, 02 Aug 2013 22:33:24 +0200
Andreas Färber afaer...@suse.de wrote:
Am 23.07.2013 18:22, schrieb Igor Mammedov:
Signed-off-by: Igor Mammedov imamm...@redhat.com
---
vl.c |7 +--
1 files changed, 1 insertions(+), 6 deletions(-)
diff --git a/vl.c b/vl.c
index
On 09/09/2013 01:13 AM, Claudio Fontana wrote:
after carefully reading and testing your patches, this is how I suggest to
proceed:
first do the implementation of the new functionality (tcg opcodes, jit) in a
way that is consistent with the existing code.
No type changes, no refactoring,
On Mon, 2013-09-09 at 16:58 +0300, Michael S. Tsirkin wrote:
On Mon, Sep 09, 2013 at 03:43:49PM +0300, Marcel Apfelbaum wrote:
On Mon, 2013-09-09 at 15:23 +0300, Michael S. Tsirkin wrote:
On Mon, Sep 09, 2013 at 03:11:55PM +0300, Marcel Apfelbaum wrote:
On Mon, 2013-09-09 at 14:40 +0300,
On Mon, 2013-09-09 at 17:04 +0300, Michael S. Tsirkin wrote:
On Mon, Sep 09, 2013 at 04:29:04PM +0300, Marcel Apfelbaum wrote:
On Mon, 2013-09-09 at 14:19 +0100, Peter Maydell wrote:
On 9 September 2013 14:15, Marcel Apfelbaum marce...@redhat.com wrote:
On Mon, 2013-09-09 at 14:02 +0100,
On 9 September 2013 15:04, Marcel Apfelbaum marce...@redhat.com wrote:
By the way, I am not sure that the upstream transactions (DMA)
can actually end with a master abort. Master abort would happen
if a transaction will not be claimed by any device on the bus.
But in DMA transactions, maybe
1 - 100 of 213 matches
Mail list logo
