On Tue, 15 Oct 2013 11:14:36 +0200
Gerd Hoffmann kra...@redhat.com wrote:
Hi,
What is the state of the qemu side patches btw?
I've them ready but they conflict with you 1Tb in e820 RFC,
I can post relevant patches as soon as we agree on this topic.
May I pick up your patch and post
On 15 October 2013 13:24, Markus Armbruster arm...@redhat.com wrote:
To go beyond RFC with this series, I need to explain why TYPE_CPU
cannot_instantiate_with_device_add_yet.
...isn't this just because it's an abstract type?
-- PMM
On Tue, Oct 15, 2013 at 12:04:05PM +0200, Gerd Hoffmann wrote:
Hi,
It's probably going to be a bit tough this time. We are pretty late in
the qemu 1.7 devel cycle, soft freeze today, and a big chunk of code
(ahci-tables-from qemu) which needs seabios support[1] is just about to
be
Paolo, or maybe Andreas,
To go beyond RFC with this series, I need to explain why isa-i8259 and
kvm-i8259 cannot_instantiate_with_device_add_yet, or drop that. I'd
appreciate your help.
Both are derived from TYPE_PIC_COMMON, which is derived from
TYPE_ISA_DEVICE.
I figure isa-i8259
Ping
http://patchwork.ozlabs.org/patch/281527/
Regards,
Petar
From: Petar Jovanovic [petar.jovano...@rt-rk.com]
Sent: Tuesday, October 08, 2013 7:32 PM
To: qemu-devel@nongnu.org
Cc: Petar Jovanovic; aurel...@aurel32.net; riku.voi...@linaro.org;
On 10/14/13 10:18, Phi Debian wrote:
Hi All,
I tried to subscribe to this list, but never got teh confirm mail.
So I write here non subscribed, so add my email addr in replies.
I am trying to use guest-dump-memory on arm (arm32, armv7* name it)
with qemu 1.6.1. The command is
On 21 July 2013 13:52, Anthony Liguori aligu...@us.ibm.com wrote:
Peter Maydell peter.mayd...@linaro.org writes:
I've just noticed that this is still inconsistent. That
page says:
Soft feature freeze. Major features should have initial code
committed by this date.
but it links to
Il 15/10/2013 14:43, Markus Armbruster ha scritto:
Paolo, or maybe Andreas,
To go beyond RFC with this series, I need to explain why isa-i8259 and
kvm-i8259 cannot_instantiate_with_device_add_yet, or drop that. I'd
appreciate your help.
Both are derived from TYPE_PIC_COMMON, which is
Also sort the test-* entries in the latter.
Signed-off-by: Laszlo Ersek ler...@redhat.com
---
.gitignore | 9 -
tests/.gitignore | 11 +--
2 files changed, 9 insertions(+), 11 deletions(-)
diff --git a/.gitignore b/.gitignore
index 8e1b73f..7f4c106 100644
--- a/.gitignore
Hi Markus,
Am 15.10.2013 14:24, schrieb Markus Armbruster:
To go beyond RFC with this series, I need to explain why TYPE_CPU
cannot_instantiate_with_device_add_yet. Would you be so kind and help
me out with a suitable comment?
From what I remember this was done when I started the whole
Andreas,
To go beyond RFC with this series, I need to explain why the IDE
controller functions of southbridges piix3-ide, piix3-ide-xen, piix4-ide
and via-ide cannot_instantiate_with_device_add_yet, or drop that. I'd
appreciate your help.
Our modelling of PCI devices is weird, to put it
On 16 September 2013 13:50, alex.ben...@linaro.org wrote:
From: Alex Bennée a...@bennee.com
Commit 9b8c69243 broke the ability to boot the kernel as the value
returned by unassigned_mem_read returned non-zero and left the kernel
looping forever waiting for it to change (see
On Tue, 15 Oct 2013 10:58:39 +0800
Fam Zheng f...@redhat.com wrote:
This file is moved out from QMP/ to BUILD dir, change the ignore file
too.
Signed-off-by: Fam Zheng f...@redhat.com
Reviewed-by: Luiz Capitulino lcapitul...@redhat.com
PS: Assuming this will be taken by Michael.
---
Am 15.10.2013 15:21, schrieb Markus Armbruster:
Andreas,
To go beyond RFC with this series, I need to explain why the IDE
controller functions of southbridges piix3-ide, piix3-ide-xen, piix4-ide
and via-ide cannot_instantiate_with_device_add_yet, or drop that. I'd
appreciate your help.
On 10/15/2013 08:36 PM, Eric Blake wrote:
On 10/14/2013 11:07 PM, Stefan Weil wrote:
Is it reasonable to get a random mac address in your guest? I don't
think so. It would no longer be possible to connect to a guest using
ssh, restart that guest and connect again with ssh.
Agreed - libvirt
Ping^2, seven weeks after initial post and code review.
Frankly, our mechanism for committing patches which aren't
obviously localised to a specific subsystem sucks :-(
It seems like pretty much every time it takes multiple
pings and a month or two before anything gets into the tree.
(at least
)
are available in the git repository at:
git://github.com/OSLL/qemu-xtensa.git tags/20131015-xtensa
for you to fetch changes up to ca529f8e13557cc2feb2eee3872d422712d9bcb0:
target-xtensa: add in_asm logging (2013-10-15 17:23:46 +0400
On Mo, 2013-10-14 at 15:42 -0700, Anthony Liguori wrote:
Michael S. Tsirkin m...@redhat.com writes:
Anthony, I know you wanted to review some of the patches,
since you didn't respond either all's well or you
could not find the time.
I think we are better off merging them for 1.7 and
On Mon, Oct 14, 2013 at 10:28 PM, Michael S. Tsirkin m...@redhat.com wrote:
On Mon, Oct 14, 2013 at 03:42:37PM -0700, Anthony Liguori wrote:
Michael S. Tsirkin m...@redhat.com writes:
Anthony, I know you wanted to review some of the patches,
since you didn't respond either all's well or you
Juan Quintela quint...@redhat.com wrote:
Hi
Please, send any topic that you are interested in covering.
Last week I forgot to send the call for topics. We still have a topic there.
There are no topics for Today agenda, so no call.
Later, Juan.
On Tue, Oct 15, 2013 at 6:43 AM, Gerd Hoffmann kra...@redhat.com wrote:
On Mo, 2013-10-14 at 15:42 -0700, Anthony Liguori wrote:
Michael S. Tsirkin m...@redhat.com writes:
Anthony, I know you wanted to review some of the patches,
since you didn't respond either all's well or you
could not
Il 15/10/2013 15:51, Anthony Liguori ha scritto:
From 41/43:
The interface is actually backwards-compatible with
existing PIIX4 ACPI (though not migration compatible).
And does AFAIK translate to, I have tested migration from new and
old and old and new with this series? I suspect the
Peter Maydell peter.mayd...@linaro.org writes:
On 15 October 2013 13:24, Markus Armbruster arm...@redhat.com wrote:
To go beyond RFC with this series, I need to explain why TYPE_CPU
cannot_instantiate_with_device_add_yet.
...isn't this just because it's an abstract type?
Abstract types have
On Tue, 15 Oct 2013 06:51:30 -0700
Anthony Liguori anth...@codemonkey.ws wrote:
On Mon, Oct 14, 2013 at 10:28 PM, Michael S. Tsirkin m...@redhat.com wrote:
On Mon, Oct 14, 2013 at 03:42:37PM -0700, Anthony Liguori wrote:
Michael S. Tsirkin m...@redhat.com writes:
Anthony, I know you
On 10/15/2013 07:10 AM, Laszlo Ersek wrote:
Also sort the test-* entries in the latter.
Signed-off-by: Laszlo Ersek ler...@redhat.com
---
.gitignore | 9 -
tests/.gitignore | 11 +--
2 files changed, 9 insertions(+), 11 deletions(-)
This feels backwards to me. I'd
On Mo, 2013-10-14 at 15:42 -0700, Anthony Liguori wrote:
Michael S. Tsirkin m...@redhat.com writes:
Anthony, I know you wanted to review some of the patches,
since you didn't respond either all's well or you
could not find the time.
I think we are better off merging them for 1.7 and
On Tue, Oct 15, 2013 at 06:51:30AM -0700, Anthony Liguori wrote:
On Mon, Oct 14, 2013 at 10:28 PM, Michael S. Tsirkin m...@redhat.com wrote:
On Mon, Oct 14, 2013 at 03:42:37PM -0700, Anthony Liguori wrote:
Michael S. Tsirkin m...@redhat.com writes:
Anthony, I know you wanted to review
On Tue, Oct 15, 2013 at 7:01 AM, Paolo Bonzini pbonz...@redhat.com wrote:
Il 15/10/2013 15:51, Anthony Liguori ha scritto:
From 41/43:
The interface is actually backwards-compatible with
existing PIIX4 ACPI (though not migration compatible).
And does AFAIK translate to, I have tested
On Tue, Oct 15, 2013 at 06:53:54AM -0700, Anthony Liguori wrote:
On Tue, Oct 15, 2013 at 6:43 AM, Gerd Hoffmann kra...@redhat.com wrote:
On Mo, 2013-10-14 at 15:42 -0700, Anthony Liguori wrote:
Michael S. Tsirkin m...@redhat.com writes:
Anthony, I know you wanted to review some of the
On Tue, Oct 15, 2013 at 7:20 AM, Michael S. Tsirkin m...@redhat.com wrote:
On Tue, Oct 15, 2013 at 06:51:30AM -0700, Anthony Liguori wrote:
On Mon, Oct 14, 2013 at 10:28 PM, Michael S. Tsirkin m...@redhat.com wrote:
On Mon, Oct 14, 2013 at 03:42:37PM -0700, Anthony Liguori wrote:
Michael S.
On 12 September 2013 11:17, Peter Maydell peter.mayd...@linaro.org wrote:
This patch series adds a 'virt' platform which uses the
kernel's mach-virt (fully device-tree driven) support
to create a simple minimalist platform intended for
use for KVM VM guests.
The major change here is that
On Tue, Oct 15, 2013 at 07:17:59AM -0700, Anthony Liguori wrote:
On Tue, Oct 15, 2013 at 7:01 AM, Paolo Bonzini pbonz...@redhat.com wrote:
Il 15/10/2013 15:51, Anthony Liguori ha scritto:
From 41/43:
The interface is actually backwards-compatible with
existing PIIX4 ACPI (though not
peter.mayd...@linaro.org writes:
On 16 September 2013 13:50, alex.ben...@linaro.org wrote:
From: Alex Bennée a...@bennee.com
Commit 9b8c69243 broke the ability to boot the kernel as the value
returned by unassigned_mem_read returned non-zero and left the kernel
looping forever waiting for
On Tue, Oct 15, 2013 at 07:21:34AM -0700, Anthony Liguori wrote:
On Tue, Oct 15, 2013 at 7:20 AM, Michael S. Tsirkin m...@redhat.com wrote:
On Tue, Oct 15, 2013 at 06:51:30AM -0700, Anthony Liguori wrote:
On Mon, Oct 14, 2013 at 10:28 PM, Michael S. Tsirkin m...@redhat.com
wrote:
On
On 15 October 2013 15:25, Alex Bennée alex.ben...@linaro.org wrote:
peter.mayd...@linaro.org writes:
This sounds like the code was written based on the kernel, not
on the board docs, which is wrong, so I think it could use
rephrasing. There's no need to mention previous behaviour either
IMHO
Il 14/10/2013 17:01, Michael S. Tsirkin ha scritto:
-VMSTATE_STRUCT(pci0_status, PIIX4PMState, 2, vmstate_pci_status,
- struct pci_status),
+VMSTATE_STRUCT_TEST(pci0_status, PIIX4PMState,
+vmstate_test_no_use_acpi_pci_hotplug,
On Tue, Oct 15, 2013 at 04:31:31PM +0200, Paolo Bonzini wrote:
Il 14/10/2013 17:01, Michael S. Tsirkin ha scritto:
-VMSTATE_STRUCT(pci0_status, PIIX4PMState, 2, vmstate_pci_status,
- struct pci_status),
+VMSTATE_STRUCT_TEST(pci0_status, PIIX4PMState,
On Tue, Oct 15, 2013 at 07:21:34AM -0700, Anthony Liguori wrote:
I cannot reasonable revert a series like this before we cut GA.
It's very simple actually.
Here's a patch to disable it all.
diff --git a/hw/i386/pc_piix.c b/hw/i386/pc_piix.c
index 63ae2ae..1a5a70c 100644
--- a/hw/i386/pc_piix.c
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
Am 15.10.2013 um 15:31 hat Andreas Färber geschrieben:
Am 15.10.2013 15:21, schrieb Markus Armbruster:
Andreas,
To go beyond RFC with this series, I need to explain why the IDE
controller functions of southbridges piix3-ide, piix3-ide-xen, piix4-ide
and via-ide
The documentation of how overlapping memory regions behave and how
the priority system works was rather brief, and confusion about
priorities seems to be quite common for developers trying to understand
how the memory region system works, so expand and clarify it.
This includes a worked example
Ping^2!
thanks
-- PMM
On 27 September 2013 04:02, Peter Maydell peter.mayd...@linaro.org wrote:
Ping!
thanks
-- PMM
On 14 September 2013 02:25, Peter Maydell peter.mayd...@linaro.org wrote:
This is based on a set of patches by Ákos Kovács which were
lurking at the beginning of his
On Tue, Oct 15, 2013 at 07:21:34AM -0700, Anthony Liguori wrote:
Please put together a summary of the testing this series has gone
through. I still think there should be automated testing as part of
this but if the manual testing is sufficiently thorough I'll
reconsider for 1.7.
Regards,
Il 15/10/2013 16:35, Michael S. Tsirkin ha scritto:
On Tue, Oct 15, 2013 at 04:31:31PM +0200, Paolo Bonzini wrote:
Il 14/10/2013 17:01, Michael S. Tsirkin ha scritto:
-VMSTATE_STRUCT(pci0_status, PIIX4PMState, 2, vmstate_pci_status,
- struct pci_status),
+
On Tue, Oct 15, 2013 at 04:50:24PM +0200, Paolo Bonzini wrote:
Il 15/10/2013 16:35, Michael S. Tsirkin ha scritto:
On Tue, Oct 15, 2013 at 04:31:31PM +0200, Paolo Bonzini wrote:
Il 14/10/2013 17:01, Michael S. Tsirkin ha scritto:
-VMSTATE_STRUCT(pci0_status, PIIX4PMState, 2,
On 10/15/2013 08:42 AM, Peter Maydell wrote:
The documentation of how overlapping memory regions behave and how
the priority system works was rather brief, and confusion about
priorities seems to be quite common for developers trying to understand
how the memory region system works, so expand
This series fixes hot-unplug of virtio devices, which can crash due to
dangling pointer accesses.
The current implementation supports guest-initiated hot-unplug via the
virtio_bus_destroy_device function, but not hot-unplugging the virtio
device by virtue of unplugging its parent container
Am 15.10.2013 16:41, schrieb Kevin Wolf:
having two IDE controllers using the same I/O ports won't work,
obviously. So if you would allow -device or device-add for them, you'd
need options to configure the ports at least.
Or a new can_only_be_instantiated_once flag. :)
Or proper error handling
The vdev field is complicated to synchronize. Just access the
BusState's list of children.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/virtio/virtio-bus.c | 63 +-
hw/virtio/virtio-mmio.c| 9 +++---
This ensures hot-unplug is handled properly by the proxy.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/char/virtio-serial-bus.c | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/hw/char/virtio-serial-bus.c
Similar to the PCI bug that prompted these patches, virtio-ccw will
segfault after the reworking of hotplug/hot-unplug. Prepare for
this by moving virtio_ccw_stop_ioeventfd to before the freeing
of the proxy device.
A better place for this could be the device_unplugged callback
for the
The vdev field is complicated to synchronize. Just access the
BusState's list of children.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/s390x/virtio-ccw.c | 80 ---
hw/s390x/virtio-ccw.h | 1 -
2 files
This ensures hot-unplug is handled properly by the proxy.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/net/virtio-net.c | 11 ---
1 file changed, 4 insertions(+), 7 deletions(-)
diff --git a/hw/net/virtio-net.c b/hw/net/virtio-net.c
index
This ensures hot-unplug is handled properly by the proxy.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/scsi/vhost-scsi.c| 11 +--
hw/scsi/virtio-scsi.c | 15 +++
include/hw/virtio/virtio-scsi.h | 2 +-
3 files
This ensures hot-unplug is handled properly by the proxy.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/block/virtio-blk.c | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/hw/block/virtio-blk.c b/hw/block/virtio-blk.c
index
This ensures hot-unplug is handled properly by the proxy.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/virtio/virtio-rng.c | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/hw/virtio/virtio-rng.c b/hw/virtio/virtio-rng.c
index
Right now we have these pairs:
- virtio_bus_plug_device/virtio_bus_destroy_device. The first
takes a VirtIODevice, the second takes a VirtioBusState
- device_plugged/device_unplug callbacks in the VirtioBusClass
(here it's just the naming that is inconsistent)
- virtio_bus_destroy_device
Il 15/10/2013 16:47, Peter Maydell ha scritto:
Ping^2!
thanks
-- PMM
I have placed this in a branch together with Fam's module patches and
will send a pull request tomorrow or Thursday (aka as soon as I get the
occasion to test Fam's patches).
Paolo
Il 15/10/2013 16:54, Michael S. Tsirkin ha scritto:
Seemed cleaner not to.
It certainly would be if we had a self-descriptive migration stream format.
However, what we have is send bytes, parse them on the destination,
hope the format matches. Hence, anything that makes the format
On 10/15/2013 08:52 AM, Eric Blake wrote:
On 10/15/2013 08:42 AM, Peter Maydell wrote:
The documentation of how overlapping memory regions behave and how
the priority system works was rather brief, and confusion about
priorities seems to be quite common for developers trying to understand
how
On 10/15/13 16:11, Eric Blake wrote:
On 10/15/2013 07:10 AM, Laszlo Ersek wrote:
Also sort the test-* entries in the latter.
Signed-off-by: Laszlo Ersek ler...@redhat.com
---
.gitignore | 9 -
tests/.gitignore | 11 +--
2 files changed, 9 insertions(+), 11
On Tue, 15 Oct 2013 16:52:42 +0200
Paolo Bonzini pbonz...@redhat.com wrote:
Similar to the PCI bug that prompted these patches, virtio-ccw will
segfault after the reworking of hotplug/hot-unplug. Prepare for
this by moving virtio_ccw_stop_ioeventfd to before the freeing
of the proxy device.
On Tue, Oct 15, 2013 at 04:54:24PM +0200, Paolo Bonzini wrote:
Il 15/10/2013 16:54, Michael S. Tsirkin ha scritto:
Seemed cleaner not to.
It certainly would be if we had a self-descriptive migration stream
format.
However, what we have is send bytes, parse them on the
On Tue, Oct 15, 2013 at 7:41 AM, Kevin Wolf kw...@redhat.com wrote:
Am 15.10.2013 um 15:31 hat Andreas Färber geschrieben:
Am 15.10.2013 15:21, schrieb Markus Armbruster:
Andreas,
To go beyond RFC with this series, I need to explain why the IDE
controller functions of southbridges
Floating point is an extension to the instruction set rather than
a coprocessor, so call it directly from the ARM and Thumb decode
functions.
Signed-off-by: Will Newton will.new...@linaro.org
---
target-arm/translate.c | 29 -
1 file changed, 24 insertions(+), 5
This adds support for the VSEL floating point selection instruction
which was added in ARMv8.
Signed-off-by: Will Newton will.new...@linaro.org
---
target-arm/translate.c | 130 -
1 file changed, 129 insertions(+), 1 deletion(-)
Changes in v5:
-
On 10/15/2013 10:50 AM, Alexey Kardashevskiy wrote:
Old kernels ( 3.1) handle hvcX devices different in different parts.
Sometime the kernel assumes that the hvc device numbers start from zero
and if there is just one hvc, then it is hvc0.
However kernel's add_preferred_console() uses the very
On 15 October 2013 15:58, Tom Sutcliffe tom.sutcli...@bromium.com wrote:
Thumbs up from me testing on Arndale. My only issue is that virt and
vexpress-a15 add virtio-mmio devices in the opposite order to each other, for
the same set of -device command line arguments. It would avoid future
Il 15/10/2013 17:07, Michael S. Tsirkin ha scritto:
Because the same version can have multiple formats depending on a datum
that is not part of the migration stream.
I see. Will it be OK if I'll update the version?
The version is constant, you cannot change it depending on which PCI
flavor
On Tue, Oct 15, 2013 at 05:09:36PM +0200, Paolo Bonzini wrote:
Il 15/10/2013 17:07, Michael S. Tsirkin ha scritto:
Because the same version can have multiple formats depending on a datum
that is not part of the migration stream.
I see. Will it be OK if I'll update the version?
The
On 15 Oct 2013, at 16:00, Peter Maydell peter.mayd...@linaro.org wrote:
On 15 October 2013 15:58, Tom Sutcliffe tom.sutcli...@bromium.com wrote:
Thumbs up from me testing on Arndale. My only issue is that virt and
vexpress-a15 add virtio-mmio devices in the opposite order to each other,
This ensures hot-unplug is handled properly by the proxy.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/virtio/virtio-balloon.c | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/hw/virtio/virtio-balloon.c
On Thu, Oct 10, 2013 at 11:15 AM, Stefan Hajnoczi stefa...@gmail.com wrote:
On Fri, Oct 04, 2013 at 07:30:45AM -0700, Mark Trumpold wrote:
On 9/26/13 10:18 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
Try the qemu-nbd --persistent option. That should prevent it from
shutting down when
This fixes a crash in hot-unplug of virtio-pci devices behind a PCIe
switch. The crash happens because the ioeventfd is still set whent the
child is destroyed (destruction happens in postorder). Then the proxy
tries to unset to ioeventfd, but the virtqueue structure that holds the
EventNotifier
On Tue, 15 Oct 2013 17:51:28 +0300
Michael S. Tsirkin m...@redhat.com wrote:
On Tue, Oct 15, 2013 at 07:21:34AM -0700, Anthony Liguori wrote:
Please put together a summary of the testing this series has gone
through. I still think there should be automated testing as part of
this but if
On Tue, 15 Oct 2013 16:52:44 +0200
Paolo Bonzini pbonz...@redhat.com wrote:
The vdev field is complicated to synchronize. Just access the
BusState's list of children.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/s390x/virtio-ccw.c | 80
The vdev field is complicated to synchronize. Just access the
BusState's list of children.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/virtio/virtio-pci.c | 110 +
hw/virtio/virtio-pci.h | 1 -
2 files
On Tue, Oct 15, 2013 at 05:51:28PM +0300, Michael S. Tsirkin wrote:
On Tue, Oct 15, 2013 at 07:21:34AM -0700, Anthony Liguori wrote:
Please put together a summary of the testing this series has gone
through. I still think there should be automated testing as part of
this but if the manual
'etc/pcimem64-minimum-address' will allow QEMU to communicate to BIOS
where PCI memory address space mapping starts in high memory.
Allowing BIOS start mapping 64-bit PCI BARs at address where QEMU
placed this mapping vs. hardcoded value right after highmem RAM.
That will allow QEMU to reserve
On Tue, Oct 15, 2013 at 04:52:45PM +0200, Paolo Bonzini wrote:
@@ -257,7 +271,7 @@ static void virtio_pci_stop_ioeventfd(VirtIOPCIProxy
*proxy)
static void virtio_ioport_write(void *opaque, uint32_t addr, uint32_t val)
{
VirtIOPCIProxy *proxy = opaque;
-VirtIODevice *vdev =
On 15 October 2013 15:52, Eric Blake ebl...@redhat.com wrote:
On 10/15/2013 08:42 AM, Peter Maydell wrote:
+It is valid to add subregions to a region which is not a pure container
+(that is, to an MMIO, RAM or ROM region). This means that the region
+will act like a container, except that any
On Tue, Oct 15, 2013 at 03:42:34PM +0100, Peter Maydell wrote:
The documentation of how overlapping memory regions behave and how
the priority system works was rather brief, and confusion about
priorities seems to be quite common for developers trying to understand
how the memory region system
Il 15/10/2013 17:40, Michael S. Tsirkin ha scritto:
On Tue, Oct 15, 2013 at 04:52:45PM +0200, Paolo Bonzini wrote:
@@ -257,7 +271,7 @@ static void virtio_pci_stop_ioeventfd(VirtIOPCIProxy
*proxy)
static void virtio_ioport_write(void *opaque, uint32_t addr, uint32_t val)
{
Am 11.10.2013 17:05, schrieb Kevin Wolf:
IF_NONE allows read-only, which makes forbidding it in this place
for other types pretty much pointless.
Instead, make sure that all devices for which the check would have
errored out check in their init function that they don't get a read-only
Il 11/10/2013 03:16, Fam Zheng ha scritto:
This series implements feature of shared object building as described in:
http://wiki.qemu.org/Features/Modules
The main idea behind modules is to isolate dependencies on third party
libraries from qemu executables, such as libglusterfs or librbd,
Il 15/10/2013 17:19, Cornelia Huck ha scritto:
The vdev field is complicated to synchronize. Just access the
BusState's list of children.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/s390x/virtio-ccw.c | 80
Am 15.10.2013 17:59, schrieb Kevin Wolf:
Am 15.10.2013 um 17:53 hat Stefan Weil geschrieben:
Am 11.10.2013 17:05, schrieb Kevin Wolf:
IF_NONE allows read-only, which makes forbidding it in this place
for other types pretty much pointless.
Instead, make sure that all devices for which the
On Tue, Oct 15, 2013 at 05:53:39PM +0200, Paolo Bonzini wrote:
Il 15/10/2013 17:40, Michael S. Tsirkin ha scritto:
On Tue, Oct 15, 2013 at 04:52:45PM +0200, Paolo Bonzini wrote:
@@ -257,7 +271,7 @@ static void virtio_pci_stop_ioeventfd(VirtIOPCIProxy
*proxy)
static void
Running this gives me:
quote
UST events:
-
None
/quote
Before or after running qemu. What is the mechanism lttng expects to
find out all these events?
Either the user should belong the group tracing, or launch the
lttng-sessiond daemon (lttng-sessiond -d).
+
+Create
Am 15.10.2013 um 17:53 hat Stefan Weil geschrieben:
Am 11.10.2013 17:05, schrieb Kevin Wolf:
IF_NONE allows read-only, which makes forbidding it in this place
for other types pretty much pointless.
Instead, make sure that all devices for which the check would have
errored out check in
On Tue, 16 Jul 2013 00:26:14 +0200
Igor Mammedov imamm...@redhat.com wrote:
...
+X86CPU_FEAT(feat-kvmclock,0, FEAT_KVM),
+X86CPU_FEAT(feat-kvm-nopiodelay, 1, FEAT_KVM),
+X86CPU_FEAT(feat-kvm-mmu, 2, FEAT_KVM),
+X86CPU_FEAT(feat-kvmclock2, 3, FEAT_KVM),
Paolo Bonzini pbonz...@redhat.com writes:
Il 15/10/2013 16:35, Michael S. Tsirkin ha scritto:
On Tue, Oct 15, 2013 at 04:31:31PM +0200, Paolo Bonzini wrote:
Il 14/10/2013 17:01, Michael S. Tsirkin ha scritto:
-VMSTATE_STRUCT(pci0_status, PIIX4PMState, 2, vmstate_pci_status,
-
Instead of relying on cpu_model, obtain the device tree node label
per CPU. Use DeviceClass::fw_name as source.
Whenever DeviceClass::fw_name is unknown, default to PowerPC,UNKNOWN.
As a consequence, spapr_fixup_cpu_dt() can operate on each CPU's fw_name,
obsoleting sPAPREnvironment::cpu_model,
Hello Alexey and Alex,
This series cleans up the fdt CPU nodes for -M pseries as attempted by Prerna.
v3 uses DeviceClass::fw_name for name storage exclusively, with
PowerPC,UNKNOWN
as fallback.
Regards,
Andreas
v2 - v3:
* Drop any type-based model name mangling and default to PowerPC,UNKNOWN
Set the expected values for POWER7, POWER7+, POWER8 and POWER5+.
Note that POWER5+ and POWER7+ are intentionally lacking the '+', so the
lack of a POWER7P family constitutes no problem.
Signed-off-by: Andreas Färber afaer...@suse.de
---
target-ppc/translate_init.c | 3 +++
1 file changed, 3
Il 15/10/2013 18:06, Michael S. Tsirkin ha scritto:
It's not datapath if you're using ioeventfd, is it?
Well not everyone uses dataplane/vhost.
ioeventfd does not require dataplane/vhost. Anyway for 1.8 I do want to
get rid of BusChild altogether, just not now.
Paolo
It's the same for MSIX
Similar to the PCI bug that prompted these patches, virtio-ccw will
segfault after the reworking of hotplug/hot-unplug. Prepare for
this by moving virtio_ccw_stop_ioeventfd to before the freeing
of the proxy device.
A better place for this could be the device_unplugged callback
for the
Right now we have these pairs:
- virtio_bus_plug_device/virtio_bus_destroy_device. The first
takes a VirtIODevice, the second takes a VirtioBusState
- device_plugged/device_unplug callbacks in the VirtioBusClass
(here it's just the naming that is inconsistent)
- virtio_bus_destroy_device
The vdev field is complicated to synchronize. Just access the
BusState's list of children.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/virtio/virtio-bus.c | 65 +-
hw/virtio/virtio-mmio.c| 9 +++---
This series fixes hot-unplug of virtio devices, which can crash due to
dangling pointer accesses.
The current implementation supports guest-initiated hot-unplug via the
virtio_bus_destroy_device function, but not hot-unplugging the virtio
device by virtue of unplugging its parent container
101 - 200 of 229 matches
Mail list logo
