FWD
- Forwarded message from Isaku Yamahata -
Subject: Re: [PATCH] [Seabios] Over 4GB address ranges for 64bit PCI BARs
User-Agent: Mutt/1.5.19 (2009-01-05)
Hi.
The current BAR allocation doesn't check overflow and some patches
are floating around which aren't merged yet.
There are seve
FWD
- Forwarded message from Alexey Korolev -
Subject: [PATCH] [Seabios] Over 4GB address ranges for 64bit PCI BARs
X-Mailer: Evolution 2.24.3
Hi,
We have seen some issues with 64bit PCI address and large BAR region support in
seabios.
On attempting to register a 64bit BAR of 1GB s
The following changes since commit d33ea50a958b2e050d2b28e5f17e3b55e91c6d74:
scsi-disk: Fix immediate failure of bdrv_aio_* (2010-11-04 13:54:37 +0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git uq/master
Gleb Natapov (1):
Add support for
From: Gleb Natapov
Add save/restore of MSR for migration and cpuid bit.
Signed-off-by: Gleb Natapov
Signed-off-by: Marcelo Tosatti
---
target-i386/cpu.h |1 +
target-i386/cpuid.c |2 +-
target-i386/kvm.c | 14 ++
target-i386/machine.c | 26 +++
From: Gleb Natapov
Add save/restore of MSR for migration and cpuid bit.
Signed-off-by: Gleb Natapov
Signed-off-by: Marcelo Tosatti
---
target-i386/cpu.h |1 +
target-i386/cpuid.c |2 +-
target-i386/kvm.c | 14 ++
target-i386/machine.c | 26 +++
The following changes since commit d33ea50a958b2e050d2b28e5f17e3b55e91c6d74:
scsi-disk: Fix immediate failure of bdrv_aio_* (2010-11-04 13:54:37 +0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git uq/master
Gleb Natapov (1):
Add support for
local_apics are allocated sequentially and never removed, so
we can stop any iterations that go to MAX_APICS as soon as we
hit the first NULL. Looking at a small guest running a virtio-net
workload with oprofile, this drops apic_get_delivery_bitmask()
from #3 in the profile to down in the noise.
We can't let the compiler define the alignment for qemu_cfg data.
Signed-off-by: Alex Williamson
---
hw/pc.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/hw/pc.c b/hw/pc.c
index 69b13bf..0264e3d 100644
--- a/hw/pc.c
+++ b/hw/pc.c
@@ -75,12 +75,12 @@ struct e820_en
Now that the save state handlers can return error, individual drivers
can cancel a migration if they hit an error or don't support it. This
makes the unmigratable callback redundant. Remove it and change the
only user to cancel the migration in a set_params callback, which
actually happens much e
This lets a save state handler NAK a migration or cancel if
it runs into problems.
Signed-off-by: Alex Williamson
---
block-migration.c |4 +++-
hw/hw.h |2 +-
savevm.c | 18 +++---
3 files changed, 19 insertions(+), 5 deletions(-)
diff --git a/block-mi
Carry the vmsd pre_save error reporting through pci_device_save().
Signed-off-by: Alex Williamson
---
hw/grackle_pci.c |4 +---
hw/gt64xxx.c |3 +--
hw/ivshmem.c |7 ++-
hw/openpic.c |4 +---
hw/pci.c |9 +++--
hw/pci.h |2 +-
hw/piix4
Carry pci_device_save() error through to virtio_save().
Signed-off-by: Alex Williamson
---
hw/virtio-balloon.c|6 +-
hw/virtio-blk.c|6 +-
hw/virtio-net.c|6 +-
hw/virtio-pci.c| 10 --
hw/virtio-serial-bus.c |6 +-
hw/virtio.
Some devices may not always able to save their state, allow
the save handler to return an error.
Signed-off-by: Alex Williamson
---
hw/adb.c|8 ++--
hw/ads7846.c|4 +++-
hw/arm_gic.c|4 +++-
hw/arm_timer.c |6 +
This allows vmsd based saves to also have a way to signal that
they can't be saved or migrated.
Signed-off-by: Alex Williamson
---
hw/fdc.c |3 ++-
hw/hpet.c |3 ++-
hw/hw.h |6 +++---
hw/i2c.c |3 ++-
hw/ide/core.c |
No changes from previous version
--
Our code paths for saving or migrating a VM are full of functions that
return void, leaving no opportunity for a device to cancel a migration,
either from error or incompatibility. The ivshmem driver attempted to
solve this with a no_migrate flag on the save s
pcibus_dev_print() was erroneously retrieving the device bus
number from the secondary bus number offset of the device
instead of the bridge above the device. This ends of landing
in the 2nd byte of the 3rd BAR for devices, which thankfully
is usually zero. pcibus_get_dev_path() copied this code,
When adding the length to the pseudo header, we're not properly
accounting for overflow.
From: Mark Wu
Signed-off-by: Alex Williamson
---
hw/e1000.c |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/hw/e1000.c b/hw/e1000.c
index 532efdc..677165f 100644
--- a/hw/e1000
This is an update to the original QEMU VFIO driver I sent several
months ago. Since then, I've ported it to the qemu-kvm.git tree,
and back, incorporated common msix and msi code, added irqfd
support, created an irqfd-like mechanism for EOIs, and likely
numerous other things that I've forgotten.
On Fri, Nov 05, 2010 at 05:31:38PM +0100, Markus Armbruster wrote:
> Gleb Natapov writes:
>
> > On Fri, Nov 05, 2010 at 03:04:05PM +0100, Markus Armbruster wrote:
> [...]
> >> >> >> There has been quite some discussion on "canonical path" on the list,
> >> >> >> but no consensus. Ironically, one
This needs to be reworked. It was a mostly automatic conversion that hasn't had
a review and with just some fixes in places where things broke. It was good
enough for some testing, though.
---
block/qcow2-cluster.c | 39 +++--
block/qcow2-refcount.c | 62 ++
Don't read this patch, it will be thrown away :-)
---
block.c | 30 ++
block.h |2 ++
2 files changed, 32 insertions(+), 0 deletions(-)
diff --git a/block.c b/block.c
index 985d0b7..f75da13 100644
--- a/block.c
+++ b/block.c
@@ -2053,6 +2053,36 @@ BlockDriverAIOC
---
Makefile|1 +
check-block-queue.c | 402 +++
2 files changed, 403 insertions(+), 0 deletions(-)
create mode 100644 check-block-queue.c
diff --git a/Makefile b/Makefile
index 02698e9..7e2785f 100644
--- a/Makefile
+++ b/Makefile
Instead of directly executing writes and fsyncs, queue them and execute them
asynchronously. What makes this interesting is that we can delay syncs and if
multiple syncs occur, we can merge them into one bdrv_flush.
A typical sequence in qcow2 (simple cluster allocation) looks like this:
1. Updat
Still not quite there, but should be a bit more correct than the first RFC.
I still need to add proper error handling, the rest of block-queue itself
should be fairly complete. With respect to error handling, IDE, virtio-blk and
scsi-disk can deal with failed bdrv_(aio_)flush now, so just failing t
On Fri, Nov 05, 2010 at 05:24:01PM +0100, Markus Armbruster wrote:
> Gleb Natapov writes:
>
> > On Fri, Nov 05, 2010 at 03:14:20PM +0100, Markus Armbruster wrote:
> >> Gleb Natapov writes:
> >>
> >> > On Thu, Nov 04, 2010 at 03:58:03PM +0100, Markus Armbruster wrote:
> >> >> Gleb Natapov write
On 03/11/10 18:17, Anthony Liguori wrote:
On 11/03/2010 01:03 PM, Ian Molton wrote:
Why is it better than using virtio-serial?
For one thing, it enforces the PID in kernel so the guests processes
cant screw each other over by forging the PID passed to qemu.
My current patch touches a tin
On 04/11/10 09:13, Alon Levy wrote:
On Wed, Nov 03, 2010 at 06:03:50PM +, Ian Molton wrote:
On 01/11/10 13:28, Anthony Liguori wrote:
On 11/01/2010 06:53 AM, Alon Levy wrote:
While we (speaking as part of the SPICE developers) want to have the same
support in our virtual GPU for 3d as we
Trying to boot Solaris 2.1 I get the following error message:
Unassigned mem read access of 1 byte to 0768 from f0014768
qemu: fatal: Trap 0x29 while interrupts disabled, Error state
pc: f0014768 npc: f001476c
Looks like a read access to a non-mapped memory (the NF-bit is 0). But
whe
qemu uses prctl() to set its process title. I bumped up against prctl()'s
16-character limit recently, when adding process title support to
libvirt[1][2].
The attached patch overwrites argv instead. Linux seems to maintain the
length of the original args, even when the new args are shorter and
NUL
Gleb Natapov writes:
> On Fri, Nov 05, 2010 at 03:04:05PM +0100, Markus Armbruster wrote:
[...]
>> >> >> There has been quite some discussion on "canonical path" on the list,
>> >> >> but no consensus. Ironically, one of the places where we got stuck was
>> >> >> ISA. You cut right through that
Gleb Natapov writes:
> On Fri, Nov 05, 2010 at 03:14:20PM +0100, Markus Armbruster wrote:
>> Gleb Natapov writes:
>>
>> > On Thu, Nov 04, 2010 at 03:58:03PM +0100, Markus Armbruster wrote:
>> >> Gleb Natapov writes:
>> >>
>> >> > On Thu, Nov 04, 2010 at 10:20:18AM +0100, Markus Armbruster wro
* Markus Armbruster [2010-11-05 11:11]:
> Ryan Harper writes:
>
> > * Markus Armbruster [2010-11-05 08:28]:
> >> I'd be fine with any of these:
> >>
> >> 1. A new command "device_disconnet ID" (or similar name) to disconnect
> >>device ID from any host parts. Nice touch: you don't have to
Ryan Harper writes:
> * Markus Armbruster [2010-11-05 08:28]:
>> I'd be fine with any of these:
>>
>> 1. A new command "device_disconnet ID" (or similar name) to disconnect
>>device ID from any host parts. Nice touch: you don't have to know
>>about the device's host part(s) to disconne
"Michael S. Tsirkin" writes:
> On Fri, Nov 05, 2010 at 02:27:49PM +0100, Markus Armbruster wrote:
>> I'd be fine with any of these:
>>
>> 1. A new command "device_disconnet ID" (or similar name) to disconnect
>>device ID from any host parts. Nice touch: you don't have to know
>>about th
On Fri, Nov 05, 2010 at 03:04:05PM +0100, Markus Armbruster wrote:
[skip]
> >> Passing bus numbers explicitly isn't hard either. Programmer is free to
> >> pass nonsensical numbers. For the most common case of one bus, the bus
> >> number parameter is just noise.
> > If programmer makes an error
On Fri, Nov 05, 2010 at 03:14:20PM +0100, Markus Armbruster wrote:
> Gleb Natapov writes:
>
> > On Thu, Nov 04, 2010 at 03:58:03PM +0100, Markus Armbruster wrote:
> >> Gleb Natapov writes:
> >>
> >> > On Thu, Nov 04, 2010 at 10:20:18AM +0100, Markus Armbruster wrote:
> >> >> Gleb Natapov write
* Markus Armbruster [2010-11-05 08:28]:
> Ryan Harper writes:
>
> > * Michael S. Tsirkin [2010-11-03 16:46]:
> >> On Wed, Nov 03, 2010 at 03:59:29PM -0500, Ryan Harper wrote:
> >> > * Michael S. Tsirkin [2010-11-03 13:03]:
> >> > > On Wed, Nov 03, 2010 at 12:29:10PM -0500, Ryan Harper wrote:
>
On Fri, Nov 05, 2010 at 02:27:49PM +0100, Markus Armbruster wrote:
> Ryan Harper writes:
>
> > * Michael S. Tsirkin [2010-11-03 16:46]:
> >> On Wed, Nov 03, 2010 at 03:59:29PM -0500, Ryan Harper wrote:
> >> > * Michael S. Tsirkin [2010-11-03 13:03]:
> >> > > On Wed, Nov 03, 2010 at 12:29:10PM -
Gleb Natapov writes:
> On Thu, Nov 04, 2010 at 03:58:03PM +0100, Markus Armbruster wrote:
>> Gleb Natapov writes:
>>
>> > On Thu, Nov 04, 2010 at 10:20:18AM +0100, Markus Armbruster wrote:
>> >> Gleb Natapov writes:
>> >>
>> >> > Add "deriver_name" to DeviceInfo to use in device path building
* Michael S. Tsirkin [2010-11-05 09:18]:
> On Fri, Nov 05, 2010 at 02:27:49PM +0100, Markus Armbruster wrote:
> > Ryan Harper writes:
> >
> > > * Michael S. Tsirkin [2010-11-03 16:46]:
> > >> On Wed, Nov 03, 2010 at 03:59:29PM -0500, Ryan Harper wrote:
> > >> > * Michael S. Tsirkin [2010-11-03
Gleb Natapov writes:
> On Thu, Nov 04, 2010 at 03:22:50PM +0100, Markus Armbruster wrote:
>> Gleb Natapov writes:
>>
>> > On Thu, Nov 04, 2010 at 09:46:57AM +0100, Markus Armbruster wrote:
>> >> > But why order of device creation is important? It shouldn't be if we
>> >> > want to move HW descr
On Thu, 2010-11-04 at 08:57 -0500, Michael Roth wrote:
> > This resembles vl.c's main_loop_wait() but I can see why you might want
> > your own. There is opportunity for sharing the select logic and ioh
> > callbacks but I think that could be addressed later.
> >
>
> Yup these are all basically c
Ryan Harper writes:
> * Michael S. Tsirkin [2010-11-03 16:46]:
>> On Wed, Nov 03, 2010 at 03:59:29PM -0500, Ryan Harper wrote:
>> > * Michael S. Tsirkin [2010-11-03 13:03]:
>> > > On Wed, Nov 03, 2010 at 12:29:10PM -0500, Ryan Harper wrote:
>> > > > * Markus Armbruster [2010-11-03 11:42]:
>> >
Crash indicates that the QEMU is older version. Basically client is sending
something that QEMU doesn't have support on.
We have a bug opened internally to handle this situation gracefully instead of
crashing. I will post the patch soon.
Moving to latest QEMU should resolve this issue...
Thanks,
** Changed in: qemu
Status: New => Invalid
--
VirtFS EFAULT when accessing not existing files
https://bugs.launchpad.net/bugs/655120
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in QEMU: Invalid
Bug description:
use a
Yes, it is a lot better... now only the complete machine crashes when
accessing the 9p.L mounted directory
{{{
virtio-9p.c:3448: submit_pdu: Assertion `!(handler == ((void *)0))' failed.
}}}
--
VirtFS EFAULT when accessing not existing files
https://bugs.launchpad.net/bugs/655120
You received th
On 11/04/2010 09:49 PM, Alexander Graf wrote:
>
> On 15.06.2010, at 11:15, Hannes Reinecke wrote:
>
>> Hi all,
>>
>> I've run an I/O exerciser against the megasas emulation and
>> found quite some issues, both with the HBA and the SCSI
>> emulation.
>>
>> - SG_IO returns -EDOM if the internal que
47 matches
Mail list logo
