Only pci host bus must be registered as root bus.
Signed-off-by: Isaku Yamahata
---
Changes v1 -> v2
- rebased to head.
---
hw/pci.c |8 ++--
hw/pci.h |1 +
hw/piix_pci.c |1 +
3 files changed, 4 insertions(+), 6 deletions(-)
diff --git a/hw/pci.c b/hw/pci.c
index 778
** Description changed:
- I Use Ubuntu 32 bit 10.04 with standerd kvm.
- I have E7600 @ 3.06GHz processor with VMX
+ I Use Ubuntu 32 bit 10.04 with standard KVM.
+ I have Intel E7600 @ 3.06GHz processor with VMX
In this system I Run:
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/
At Thu, 17 Jun 2010 18:18:18 +0100,
Jamie Lokier wrote:
>
> Kevin Wolf wrote:
> > Am 16.06.2010 18:52, schrieb MORITA Kazutaka:
> > > At Wed, 16 Jun 2010 13:04:47 +0200,
> > > Kevin Wolf wrote:
> > >>
> > >> Am 15.06.2010 19:53, schrieb MORITA Kazutaka:
> > >>> posix-aio-compat sends a signal in a
On Thu, Jun 17, 2010 at 02:57:16PM +0300, Michael S. Tsirkin wrote:
> On Thu, Jun 17, 2010 at 01:02:43PM +0300, Michael S. Tsirkin wrote:
> > For example, forcing all devices to call pci_reset_default
> > in their reset routines does not look like a good cleanup:
> > the less boilerplate, the bette
On Thu, Jun 17, 2010 at 12:37:21PM +0300, Michael S. Tsirkin wrote:
> On Thu, Jun 17, 2010 at 03:15:51PM +0900, Isaku Yamahata wrote:
> > set PCI multi-function bit appropriately.
> >
> > Signed-off-by: Isaku Yamahata
> >
> > ---
> > changes v1 -> v2:
> > don't set header type register in config
On Thu, Jun 17, 2010 at 02:17:20PM +0300, Michael S. Tsirkin wrote:
> On Thu, Jun 17, 2010 at 08:03:08PM +0900, Isaku Yamahata wrote:
> > This patch set allows seabios to initialize multi pci bus and 64bit BAR.
> >
> > Currently seabios is able to initialize only pci root bus.
> > However multi pc
M. Mohan Kumar wrote:
> Compute iounit based on the host filesystem block size and pass it to
> client with open/create response. Also return iounit as statfs's f_bsize
> for optimal block size transfers.
>
>
> Signed-off-by: M. Mohan Kumar
> Reviewd-by: Sripathi Kodi
> ---
> hw/virtio-9p.c |
On Thu, 2010-06-17 at 23:01 +0100, Paul Brook wrote:
> > > ### Paul proposes to require all buses to define bus addresses. Make
> > > one up if necessary.
> >
> > That seems arbitrary and prone to breakage. How do we handle a subtle
> > change in device instantiation order and still allow mi
On Wed, 2010-06-16 at 10:23 +0200, Markus Armbruster wrote:
> Alex Williamson writes:
>
> > On Tue, 2010-06-15 at 12:28 +0100, Paul Brook wrote:
> >> > > Alex proposed to disambiguate by adding "identified properties of the
> >> > > immediate parent bus and device" to the path component. For PCI
> > ### Paul proposes to require all buses to define bus addresses. Make
> > one up if necessary.
>
> That seems arbitrary and prone to breakage. How do we handle a subtle
> change in device instantiation order and still allow migration? If by
> code change or command line ordering my frobn
I'm a little bit lost at how to implement something to print these
semantics, but a couple comments below...
On Wed, 2010-06-16 at 11:46 +0200, Markus Armbruster wrote:
> A number of changes to qdev paths have been proposed in various threads.
> It's becoming harder to keep track of them, so let m
On Wed, Jun 16, 2010 at 7:54 PM, Anthony Liguori
wrote:
> On 06/16/2010 10:46 AM, Stefan Hajnoczi wrote:
>>
>> query-balloon
>> -
>>
>> Show balloon information.
>>
>> Make an asynchronous request for balloon info.
>
> s/asynchronous//. All requests are asynchronous.
It would be help
On Wed, Jun 16, 2010 at 4:45 PM, Stefan Hajnoczi
wrote:
> netdev_del
> --
>
> Remove host network device.
>
> Arguments:
>
> - "id": the device's ID, must be unique (json-string)
>
> Example:
>
> -> { "execute": "netdev_del", "arguments": { "id": "netdev1" } }
> <- { "return": {} }
What h
On Wed, Jun 16, 2010 at 4:45 PM, Stefan Hajnoczi
wrote:
> migrate_set_speed
> -
>
> Set maximum speed for migrations.
>
> Arguments:
>
> - "value": maximum speed, in bytes per second (json-number)
>
> Example:
>
> -> { "execute": "migrate_set_speed", "arguments": { "value": 1024 }
On Wed, Jun 16, 2010 at 4:45 PM, Stefan Hajnoczi
wrote:
> migrate_set_downtime
>
>
> Set maximum tolerated downtime (in seconds) for migrations.
>
> Arguments:
>
> - "value": maximum downtime (json-number)
>
> Example:
>
> -> { "execute": "migrate_set_downtime", "arguments": {
On Wed, Jun 16, 2010 at 4:45 PM, Stefan Hajnoczi
wrote:
> memsave
> ---
>
> Save to disk virtual memory dump starting at 'val' of size 'size'.
>
> Arguments:
>
> - "val": the starting address (json-int)
> - "size": the memory size, in bytes (json-int)
> - "filename": file path (json-string)
>
It is unclear how getfd works. Do you send the SCM_CREDENTIALS
ancillary data together with the getfd QMP command?
Would be nice to have this documented.
Stefan
On Thu, Jun 17, 2010 at 3:39 PM, Kevin Wolf wrote:
> Am 17.06.2010 16:19, schrieb Stefan Hajnoczi:
>> On Thu, Jun 17, 2010 at 1:03 PM, Kevin Wolf wrote:
>>> Use bdrv_(p)write_sync to ensure metadata integrity in case of a crash.
>>
>> Any performance numbers? This change is necessary for correct
On Thu, Jun 17, 2010 at 1:49 PM, Markus Armbruster wrote:
> Stefan Hajnoczi writes:
>
>> On Wed, Jun 16, 2010 at 6:27 PM, Markus Armbruster wrote:
>>> blockdev_add
>>>
>>>
>>> Add host block device.
>>>
>>> Arguments:
>>>
>>> - "id": the host block device's ID, must be unique (json-
On Fri, Jun 11, 2010 at 03:35:40PM +0200, Kevin Wolf wrote:
> Am 07.06.2010 20:00, schrieb MORITA Kazutaka:
>
> Also, I'd like to have qemu-iotests run on it before including it. IIRC,
> Christian has hacked on qemu-iotests to make it work with protocols for
> his rbd driver - Christian, can you p
Hi Simone,
sorry for the late reply. I've been on vacation for a week.
Thanks for sending the patch. At first sight your patch looks good.
I'll do some testing by the weekend.
Kevin also sent me a note about the missing aio support, but I didn't
have the time to implement it yet. Now it seems, t
Gibbons, Scott wrote:
> My architecture is an Interleaved Multithreading VLIW architecture. One
> bundle (packet) executes per processor cycle, rotating between threads (i.e.,
> thread 0 executes at time 0, thread 1 executes at time 1, then thread 0
> executes at time 2, etc.). Each thread has
On 06/17/2010 01:15 PM, Luiz Capitulino wrote:
This is a general question for all commands that can take way too long
or never return.
For QMP the question is whether we should handle this in QEMU or in the
client. Ie, if the guest doesn't respond the client could detect that
and cancel the
On Tue, 15 Jun 2010 11:03:13 +0200
Markus Armbruster wrote:
> Anthony Liguori writes:
>
> > On 06/09/2010 09:27 AM, Gerd Hoffmann wrote:
> >> Hi,
> >>
> >>> This make sense when you mistakenly add a pci device on a -s -S
> >>> scenario, like the scenario described on the following bug:
> >>>
On 06/17/2010 11:05 AM, Gibbons, Scott wrote:
> My architecture is an Interleaved Multithreading VLIW architecture.
> One bundle (packet) executes per processor cycle, rotating between
> threads (i.e., thread 0 executes at time 0, thread 1 executes at time
> 1, then thread 0 executes at time 2, etc
My architecture is an Interleaved Multithreading VLIW architecture. One bundle
(packet) executes per processor cycle, rotating between threads (i.e., thread 0
executes at time 0, thread 1 executes at time 1, then thread 0 executes at time
2, etc.). Each thread has its own context (including a
On 06/17/2010 05:09 AM, Paolo Bonzini wrote:
+while (QTAILQ_EMPTY(&(queue->request_list))&&
+ (ret != ETIMEDOUT)) {
+ret = qemu_cond_timedwait(&(queue->cond),
+ &(queue->lock), 10*10);
+}
Using qemu_cond_timedwait is a hack for not properly broadcas
On 06/17/2010 11:45 AM, Luiz Capitulino wrote:
On Thu, 17 Jun 2010 18:34:00 +0200
Juan Quintela wrote:
Luiz Capitulino wrote:
On Wed, 16 Jun 2010 21:10:04 +0200
Juan Quintela wrote:
Luiz Capitulino wrote:
On Tue, 15 Jun 2010 17:24:59 +0200
Juan Quintela wrot
Luiz Capitulino wrote:
> On Wed, 16 Jun 2010 21:10:04 +0200
> Juan Quintela wrote:
>
>> Luiz Capitulino wrote:
>> > On Tue, 15 Jun 2010 17:24:59 +0200
>> > Juan Quintela wrote:
>>
>> >> >
>> >> > I still don't see the need for MIGRATION_STARTED, it could be useful in
>> >> > the target but I'
Kevin Wolf wrote:
> Am 16.06.2010 18:52, schrieb MORITA Kazutaka:
> > At Wed, 16 Jun 2010 13:04:47 +0200,
> > Kevin Wolf wrote:
> >>
> >> Am 15.06.2010 19:53, schrieb MORITA Kazutaka:
> >>> posix-aio-compat sends a signal in aio operations, so we should
> >>> consider that fgets() could be interrup
On Thu, 17 Jun 2010 18:34:00 +0200
Juan Quintela wrote:
> Luiz Capitulino wrote:
> > On Wed, 16 Jun 2010 21:10:04 +0200
> > Juan Quintela wrote:
> >
> >> Luiz Capitulino wrote:
> >> > On Tue, 15 Jun 2010 17:24:59 +0200
> >> > Juan Quintela wrote:
> >>
> >> >> >
> >> >> > I still don't see t
Alex Williamson wrote:
> The comment suggests we're checking for the driver in the ready
> state and bus master disabled, but the code is checking that it's
> not in the ready state.
>
> Signed-off-by: Alex Williamson
> Found-by: Amit Shah
Acked-by: Juan Quintela
> ---
>
> hw/virtio-pci.c |
** Tags added: patch
--
qemu-nbd slow and missing "writeback" cache option
https://bugs.launchpad.net/bugs/595117
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in QEMU: Invalid
Status in “qemu-kvm” package in Ubuntu: Incomplete
On 06/17/2010 03:29 PM, Julian Pidancet wrote:
>
> Hi,
>
> Thanks for spotting these errors. Here is a respin of my patch to address you
> concerns.
> (The munmap call is included).
>
> Cheers,
>
> Julian
>
Oh, I actually tested the last patch only with the -nographic switch. There's
still
On Wed, Jun 16, 2010 at 06:14:35PM +0530, Prerna Saxena wrote:
> This patch adds support for dynamically enabling/disabling of tracepoints.
> This is done by internally maintaining each tracepoint's state, and
> permitting logging of data from a tracepoint only if it is in an
> 'active' state.
>
Stephane-
I understand your plight. However, according to the rules and
policies of the QEMU project, you must submit the patch on the
qemu-devel@ mailing list, in addition to (or instead of) in the bug
tracker. It's not my project, not my policy. I'm just trying to make
sure you get your patch
Alex Williamson wrote:
> The comment suggests we're checking for the driver in the ready
> state and bus master disabled, but the code is checking that it's
> not in the ready state.
>
> Signed-off-by: Alex Williamson
> Found-by: Amit Shah
> ---
>
> hw/virtio-pci.c |2 +-
> 1 files changed,
On 06/17/2010 08:12 AM, Gibbons, Scott wrote:
> Another question I have is how to handle this multithreaded
> architecture. This seems to be extraordinarily difficult as a
> dynamic translation problem and I'll probably defer it to later.
> But, if anyone has any suggestions, I'd be glad to hear t
On (Thu) Jun 17 2010 [09:15:02], Alex Williamson wrote:
> The comment suggests we're checking for the driver in the ready
> state and bus master disabled, but the code is checking that it's
> not in the ready state.
>
> Signed-off-by: Alex Williamson
> Found-by: Amit Shah
> ---
Acked-by: Amit S
On Thu, Jun 17, 2010 at 09:15:02AM -0600, Alex Williamson wrote:
> The comment suggests we're checking for the driver in the ready
> state and bus master disabled, but the code is checking that it's
> not in the ready state.
>
> Signed-off-by: Alex Williamson
> Found-by: Amit Shah
Acked-by: Mic
The comment suggests we're checking for the driver in the ready
state and bus master disabled, but the code is checking that it's
not in the ready state.
Signed-off-by: Alex Williamson
Found-by: Amit Shah
---
hw/virtio-pci.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --g
Yes, as a guest.
Thanks for the helpful suggestions. We have a closed pipeline and code errors
are caught by the assembler. Delaying writeback is most likely what I'll be
doing.
Another question I have is how to handle this multithreaded architecture. This
seems to be extraordinarily diffic
On Wed, Jun 16, 2010 at 06:12:06PM +0530, Prerna Saxena wrote:
> diff --git a/simpletrace.c b/simpletrace.c
> index 2fec4d3..239ae3f 100644
> --- a/simpletrace.c
> +++ b/simpletrace.c
> @@ -62,3 +62,16 @@ void trace4(TraceEvent event, unsigned long x1, unsigned
> long x2, unsigned long
> void tra
On Tue, 15 Jun 2010 11:30:20 -0500
Anthony Liguori wrote:
> This is the first set of commands as part of the QMP specification review.
> Please comment on the individual commands specifications and Stefan and I will
> try to fold the comments back into the command documentation.
Very nice!
A
Am 17.06.2010 16:19, schrieb Stefan Hajnoczi:
> On Thu, Jun 17, 2010 at 1:03 PM, Kevin Wolf wrote:
>> Use bdrv_(p)write_sync to ensure metadata integrity in case of a crash.
>
> Any performance numbers? This change is necessary for correctness but
> I wonder what the performance impact is for us
On Thu, 17 Jun 2010 09:58:37 -0300
Miguel Di Ciurcio Filho wrote:
> The 'info snapshots' monitor command does not show snapshot information from
> all
> available block devices.
>
> Usage example:
> $ qemu -hda disk1.qcow2 -hdb disk2.qcow2
>
> (qemu) info snapshots
> Snapshot devices: ide0-hd0
On 06/17/2010 11:43 AM, Gerd Hoffmann wrote:
>Hi,
>
> You register the display allocator, but don't unregister in
> fbdev_display_uninit().
>
> You are just lucky that fbdev_cleanup() forgets to unmap the framebuffer.
>
> Apply the attached fix, start qemu with vnc, then do "change fbdev on
On Wed, 16 Jun 2010 21:10:04 +0200
Juan Quintela wrote:
> Luiz Capitulino wrote:
> > On Tue, 15 Jun 2010 17:24:59 +0200
> > Juan Quintela wrote:
>
> >> >
> >> > I still don't see the need for MIGRATION_STARTED, it could be useful in
> >> > the target but I'd like to understand the use case in
On Thu, Jun 17, 2010 at 1:03 PM, Kevin Wolf wrote:
> Use bdrv_(p)write_sync to ensure metadata integrity in case of a crash.
Any performance numbers? This change is necessary for correctness but
I wonder what the performance impact is for users.
Stefan
Am 17.06.2010 15:01, schrieb Anthony Liguori:
> On 06/17/2010 03:20 AM, Kevin Wolf wrote:
>> Am 16.06.2010 20:07, schrieb Anthony Liguori:
>>
But it requires that
everything that -blockdev provides is accessible with -drive, too (or
that we're okay with users hating us).
On Thu, Jun 17, 2010 at 04:48:09PM +0900, Isaku Yamahata wrote:
> Thanks for the patch.
> Does vista boot with the patch eventually?
Vista boots, but is unable to allocate resources for the pcie root
ports. I'm looking into that.
--
Matthew Garrett | mj...@srcf.ucam.org
Sheng Yang wrote:
> Signed-off-by: Sheng Yang
> ---
>
> Would send out XSAVE patch after the upstream ones have been merged, since the
> patch would be affected by the merge.
>
> qemu-kvm-x86.c| 23 ++-
> qemu-kvm.c| 10 --
> qemu-kvm.h| 30
Sheng Yang wrote:
> Signed-off-by: Sheng Yang
> ---
> kvm-all.c | 21 +++
> kvm.h |2 +
> target-i386/cpu.h |7 ++-
> target-i386/kvm.c | 139
> -
> target-i386/machine.c | 20 +++
> 5 files
Michael S. Tsirkin wrote:
> pcnet enables memory/io on init, which
> does not make sense as BAR values are wrong.
> Fix this, disabling BARs according to PCI spec.
> Address other minor TODOs.
>
> Signed-off-by: Michael S. Tsirkin
> ---
>
> The following untested patch brings pcnet in
> complian
On 06/17/2010 03:20 AM, Kevin Wolf wrote:
Am 16.06.2010 20:07, schrieb Anthony Liguori:
But it requires that
everything that -blockdev provides is accessible with -drive, too (or
that we're okay with users hating us).
I'm happy for -drive to die. I think we should support -hda
The 'info snapshots' monitor command does not show snapshot information from all
available block devices.
Usage example:
$ qemu -hda disk1.qcow2 -hdb disk2.qcow2
(qemu) info snapshots
Snapshot devices: ide0-hd0
Snapshot list (from ide0-hd0):
IDTAG VM SIZEDA
2010-06-16 20:36:00 -, Dustin Kirkland:
[...]
> Could you please send that patch to the qemu-devel@ mailing list?
> Thanks!
[...]
Hi Dustin, it looks like qemu-devel is subscribed to bugs in
there, so the bug report is on the list already.
Note that I still consider it as a bug because:
- s
Stefan Hajnoczi writes:
> On Wed, Jun 16, 2010 at 6:27 PM, Markus Armbruster wrote:
>> blockdev_add
>>
>>
>> Add host block device.
>>
>> Arguments:
>>
>> - "id": the host block device's ID, must be unique (json-string)
>> - "format": image format (json-string, optional)
>> - Pos
Use bdrv_(p)write_sync to ensure metadata integrity in case of a crash.
Signed-off-by: Kevin Wolf
---
block/qcow2-cluster.c | 16
block/qcow2-refcount.c | 18 +-
block/qcow2-snapshot.c | 14 +++---
block/qcow2.c | 10 +-
4 files
Add new functions that write and flush the written data to disk immediately.
This is what needs to be used for image format metadata to maintain integrity
for cache=... modes that don't use O_DSYNC. (Actually, we only need barriers,
and therefore the functions are defined as such, but flushes is wh
This addresses the data integrity problems described at
http://wiki.qemu.org/Features/Qcow2DataIntegrity#Metadata_update_ordering.2C_Part_2
These problems are the same for all image formats (except raw, which doesn't
have any metadata), so I'm going to add more patches for the other formats for
th
On Thu, Jun 17, 2010 at 01:02:43PM +0300, Michael S. Tsirkin wrote:
> For example, forcing all devices to call pci_reset_default
> in their reset routines does not look like a good cleanup:
> the less boilerplate, the better IMO.
One thing that we need to address, is devices
which need to enable m
On Thu, Jun 17, 2010 at 08:03:08PM +0900, Isaku Yamahata wrote:
> This patch set allows seabios to initialize multi pci bus and 64bit BAR.
>
> Currently seabios is able to initialize only pci root bus.
> However multi pci bus support is wanted because
> - more pci bus is wanted in qemu for many
pcnet enables memory/io on init, which
does not make sense as BAR values are wrong.
Fix this, disabling BARs according to PCI spec.
Address other minor TODOs.
Signed-off-by: Michael S. Tsirkin
---
The following untested patch brings pcnet in
compliance with the spec.
Could someone who's interest
Make init value for this register match the spec.
BAR address is 0 at init, so enabling it
only works by chance.
Signed-off-by: Michael S. Tsirkin
---
This patch is untested. Could someone who has vmware
guests please look at it?
Thanks!
hw/vmware_vga.c |3 ---
1 files changed, 0 insertion
make pci memory space assignment 64bit aware.
If 64bit memory space is found while assigning pci memory space,
clear higher bit and skip to next bar.
This patch is preparation for q35 chipset initialization which
has 64bit bar.
Signed-off-by: Isaku Yamahata
---
src/pciinit.c | 19
This patch makes pci bar offset calculation pci bridge aware.
The offset of pci bridge rom is different from normal device.
Signed-off-by: Isaku Yamahata
---
src/pciinit.c |6 +-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/src/pciinit.c b/src/pciinit.c
index 6ba51f2..1
initialize pci bridge filtering registers.
Signed-off-by: Isaku Yamahata
---
src/pciinit.c | 117 +++-
1 files changed, 114 insertions(+), 3 deletions(-)
diff --git a/src/pciinit.c b/src/pciinit.c
index fe6848a..f68a690 100644
--- a/src/pciin
This patch factors out bar offset calculation.
Later the calculation logic will be enhanced.
Signed-off-by: Isaku Yamahata
---
src/pciinit.c | 20 ++--
1 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/src/pciinit.c b/src/pciinit.c
index b6ab157..6ba51f2 100644
-
Make pci bar assigner preferchable memory aware.
This is needed for PCI bridge support because memory space and
prefetchable memory space is filtered independently based on
memory base/limit and prefetchable memory base/limit of pci bridge.
On bus 0, such a distinction isn't necessary so keep exist
This patch introduces foreachpci_in_bus() helper macro for
depth first recursion. foreachpci() is for width first recursion.
The macro will be used later to initialize pci bridge
that requires depth first recursion.
Signed-off-by: Isaku Yamahata
---
src/pci.c | 30 +
On Thu, Jun 17, 2010 at 03:15:45PM +0900, Isaku Yamahata wrote:
> fix pci_device_reset() with 64bit BAR.
> export pci_bus_reset(), pci_device_reset() and two helper functions
> for later use. And several clean ups.
>
> Signed-off-by: Isaku Yamahata
> ---
> hw/pci.c | 44 +++
factor out pci bar region allocation logic.
Signed-off-by: Isaku Yamahata
---
src/pciinit.c | 84 -
1 files changed, 47 insertions(+), 37 deletions(-)
diff --git a/src/pciinit.c b/src/pciinit.c
index 0556ee2..488c77b 100644
--- a/src/pci
pci bridge bus initialization.
Signed-off-by: Isaku Yamahata
---
src/pciinit.c | 70 +
1 files changed, 70 insertions(+), 0 deletions(-)
diff --git a/src/pciinit.c b/src/pciinit.c
index 1c2c8c6..fe6848a 100644
--- a/src/pciinit.c
+++ b/s
This patch set allows seabios to initialize multi pci bus and 64bit BAR.
Currently seabios is able to initialize only pci root bus.
However multi pci bus support is wanted because
- more pci bus is wanted in qemu for many slots
- pci express support is commin in qemu which requires multi pci b
do not fuck me about 'spamsender' machine name. I never send spam. it's
just our mail server :)
--
segmentation scsi writeback
https://bugs.launchpad.net/bugs/595438
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in QEMU: New
Public bug reported:
I Use Ubuntu 32 bit 10.04 with standerd kvm.
I have E7600 @ 3.06GHz processor with VMX
In this system I Run:
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
QEMU_AUDIO_DRV=none /usr/bin/kvm -M pc-0.12 -enable-kvm -m 256 -smp 1 -name
spamsender -u
Bug 100% reproductible (on this, and on other machine with different
processor)
core dump (bzip2) attached
** Attachment added: "core dump"
http://launchpadlibrarian.net/50482028/core.bz2
--
segmentation scsi writeback
https://bugs.launchpad.net/bugs/595438
You received this bug notificati
** Summary changed:
- segmentation scsi writeback
+ KVM segmentation fault, using SCSI+writeback and linux 2.4 guest
--
KVM segmentation fault, using SCSI+writeback and linux 2.4 guest
https://bugs.launchpad.net/bugs/595438
You received this bug notification because you are a member of qemu-
de
Hi,
+static void fbdev_free_displaysurface(DisplaySurface *surface)
+{
+if (surface == NULL)
+return;
+
+if (surface->flags& QEMU_ALLOCATED_FLAG) {
+qemu_free(surface->data);
+}
+
+surface->data = NULL;
This is pretty pointless ...
+qemu_free(surface);
On Wed, Jun 16, 2010 at 6:27 PM, Markus Armbruster wrote:
> blockdev_add
>
>
> Add host block device.
>
> Arguments:
>
> - "id": the host block device's ID, must be unique (json-string)
> - "format": image format (json-string, optional)
> - Possible values: "raw", "qcow2", ...
Wha
On Thu, Jun 17, 2010 at 03:15:47PM +0900, Isaku Yamahata wrote:
> helper function to add ssvid capability.
>
> Signed-off-by: Isaku Yamahata
But .. this is unused?
> ---
> hw/pci_bridge.c | 20
> hw/pci_bridge.h |3 +++
> 2 files changed, 23 insertions(+), 0 deletion
On Thu, Jun 17, 2010 at 03:15:44PM +0900, Isaku Yamahata wrote:
> export qdev_reset() for later use.
>
> Signed-off-by: Isaku Yamahata
> ---
> hw/qdev.c | 13 +
> hw/qdev.h |1 +
> 2 files changed, 10 insertions(+), 4 deletions(-)
>
> diff --git a/hw/qdev.c b/hw/qdev.c
> index
+while (QTAILQ_EMPTY(&(queue->request_list))&&
+ (ret != ETIMEDOUT)) {
+ret = qemu_cond_timedwait(&(queue->cond),
+ &(queue->lock), 10*10);
+}
Using qemu_cond_timedwait is a hack for not properly broadcasting the
On Thu, Jun 17, 2010 at 03:15:42PM +0900, Isaku Yamahata wrote:
> This patch series cleans up pci to pci bridge layer by introducing
> pci bridge layer. and some bug fixes.
> Although pci bridge implementation would belong to pci.c,
> I split it out into pci_bridge.c because pci.c is already big en
Signed-off-by: Sheng Yang
---
Would send out XSAVE patch after the upstream ones have been merged, since the
patch would be affected by the merge.
qemu-kvm-x86.c| 23 ++-
qemu-kvm.c| 10 --
qemu-kvm.h| 30 --
tar
On Thu, Jun 17, 2010 at 03:15:46PM +0900, Isaku Yamahata wrote:
> introduce pci bridge layer.
> export pci_bridge_write_config() for generic use.
> support device reset and bus reset of bridge control.
> convert apb bridge and dec p2p bridge to use new pci bridge layer.
> save/restore is supported
Signed-off-by: Sheng Yang
---
kvm-all.c | 21 +++
kvm.h |2 +
target-i386/cpu.h |7 ++-
target-i386/kvm.c | 139 -
target-i386/machine.c | 20 +++
5 files changed, 186 insertions(+), 3 deleti
On Thu, Jun 17, 2010 at 03:15:52PM +0900, Isaku Yamahata wrote:
> Don't overwrite pci header type.
> Otherwise, multi function bit which pci_init_header_type() sets
> appropriately is lost.
> Anyway PCI_HEADER_TYPE_NORMAL is zero, so it is unnecessary to zero
> which is already zero cleared.
>
> S
On Thu, Jun 17, 2010 at 03:15:51PM +0900, Isaku Yamahata wrote:
> set PCI multi-function bit appropriately.
>
> Signed-off-by: Isaku Yamahata
>
> ---
> changes v1 -> v2:
> don't set header type register in configuration space.
> ---
> hw/pci.c | 25 +
> 1 files changed
On Thu, Jun 17, 2010 at 10:59:01AM +0200, Jan Kiszka wrote:
> Gleb Natapov wrote:
> > On Thu, Jun 17, 2010 at 10:42:34AM +0200, Jan Kiszka wrote:
> >> Gleb Natapov wrote:
> >>> On Thu, Jun 17, 2010 at 10:30:15AM +0200, Jan Kiszka wrote:
> > Sorry, I lost you here. What "works for IO-based fw-cf
On Wed, Jun 16, 2010 at 06:06:35PM +0200, Corentin Chary wrote:
> On Wed, Jun 16, 2010 at 5:52 PM, Anthony Liguori
> wrote:
> > On 06/16/2010 10:47 AM, Corentin Chary wrote:
> >>
> >> I would need something like flush_threadlet_queue for the vnc server.
> >> I need it in
> >> vnc_disconnect(), vnc
On Wed, Jun 16, 2010 at 10:20:36AM -0500, Anthony Liguori wrote:
> On 06/16/2010 09:52 AM, Paolo Bonzini wrote:
>> BTW it's obviously okay with signaling the condition when a threadlet is
>> submitted. But when something affects all queue's workers
>> (flush_threadlet_queue) you want a broadcast
Sheng Yang wrote:
> Signed-off-by: Sheng Yang
> ---
> target-i386/cpu.h |7 ++-
> target-i386/kvm.c | 139
> -
> target-i386/machine.c | 20 +++
> 3 files changed, 163 insertions(+), 3 deletions(-)
>
> diff --git a/target-i386/c
Gleb Natapov wrote:
> On Thu, Jun 17, 2010 at 10:42:34AM +0200, Jan Kiszka wrote:
>> Gleb Natapov wrote:
>>> On Thu, Jun 17, 2010 at 10:30:15AM +0200, Jan Kiszka wrote:
> Sorry, I lost you here. What "works for IO-based fw-cfg, but not for
> MMIO-based".
Undefined IO ports return -1, u
On Thu, Jun 17, 2010 at 10:42:34AM +0200, Jan Kiszka wrote:
> Gleb Natapov wrote:
> > On Thu, Jun 17, 2010 at 10:30:15AM +0200, Jan Kiszka wrote:
> >>> Sorry, I lost you here. What "works for IO-based fw-cfg, but not for
> >>> MMIO-based".
> >> Undefined IO ports return -1, undefined (/wrt read acc
On Wed, Jun 16, 2010 at 09:22:09PM -0400, Kevin O'Connor wrote:
> On Tue, Jun 15, 2010 at 09:37:07AM +0300, Gleb Natapov wrote:
> > On Mon, Jun 14, 2010 at 04:12:32PM -0400, Kevin O'Connor wrote:
> > > But.. in order to move to a newer ACPI spec, there would be qemu
> > > changes anyway. (If nothi
On Wed, Jun 16, 2010 at 02:34:16PM +0200, Paolo Bonzini wrote:
>> +block-obj-y += qemu-thread.o
>> +block-obj-y += async-work.o
>
> These should be (at least for now) block-obj-$(CONFIG_POSIX).
Right. Will fix that.
>
>> +while (QTAILQ_EMPTY(&(queue->request_list))&&
>> + (re
Sheng Yang wrote:
> On Thursday 17 June 2010 15:41:43 Jan Kiszka wrote:
>> Sheng Yang wrote:
>>> Based on upstream xsave related fields.
>>>
>>> Signed-off-by: Sheng Yang
>>> ---
>>>
>>> qemu-kvm-x86.c | 95
>>> +++- qemu-kvm.c
>>> | 24
Gleb Natapov wrote:
> On Thu, Jun 17, 2010 at 10:30:15AM +0200, Jan Kiszka wrote:
>>> Sorry, I lost you here. What "works for IO-based fw-cfg, but not for
>>> MMIO-based".
>> Undefined IO ports return -1, undefined (/wrt read access) MMIO 0. So
>> you need to select a key that is different from bot
1 - 100 of 120 matches
Mail list logo
