If llistxattr returned 0, qemu aborts.
Signed-off-by: Kusanagi Kouichi
---
hw/virtio-9p-xattr.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/hw/virtio-9p-xattr.c b/hw/virtio-9p-xattr.c
index 175f372..1aab081 100644
--- a/hw/virtio-9p-xattr.c
+++ b/hw/virtio-9p-xattr
Cher Monsieur
C'est avec plaisir que je m'adresse à ma lettre, je suis HAJI Barry Aminata l'épouse de feu le général de la Guinée.
Mon mari a été assassiné pour des raisons politiques en Guinée. Et avant sa mort, il avait gagné et un contrat avec le gouvernement d'une très grande quantité d'arg
On Fri, 29 Oct 2010, Blue Swirl wrote:
> On Fri, Oct 29, 2010 at 7:30 PM, malc wrote:
> >
> > c57c846a80f9306aa2c6cf7efdef45ed42723fac broke gus, Blue Swirl said that
> > he put muldiv64 into qemu-timer.h since putting it elsewhere broke
> > something and he can't remember what, anyways gus has n
On Fri, Oct 29, 2010 at 7:30 PM, malc wrote:
>
> c57c846a80f9306aa2c6cf7efdef45ed42723fac broke gus, Blue Swirl said that
> he put muldiv64 into qemu-timer.h since putting it elsewhere broke
> something and he can't remember what, anyways gus has nothing to do with
> timers (just like muldiv64) so
On Fri, 2010-10-29 at 19:57 +, Blue Swirl wrote:
> On Fri, Oct 29, 2010 at 4:39 PM, Alex Williamson
> wrote:
> > This adds a minimum chunk of Anthony's RAM API support so that we
> > can identify actual VM RAM versus all the other things that make
> > use of qemu_ram_alloc.
> >
> > Signed-off-
On Fri, Oct 29, 2010 at 4:39 PM, Alex Williamson
wrote:
> This adds a minimum chunk of Anthony's RAM API support so that we
> can identify actual VM RAM versus all the other things that make
> use of qemu_ram_alloc.
>
> Signed-off-by: Alex Williamson
> ---
>
> Makefile.target | 1 +
> cpu-com
c57c846a80f9306aa2c6cf7efdef45ed42723fac broke gus, Blue Swirl said that
he put muldiv64 into qemu-timer.h since putting it elsewhere broke
something and he can't remember what, anyways gus has nothing to do with
timers (just like muldiv64) so I've tried following and built all targets
on linux wi
On 10/29/2010 12:56 PM, Alex Williamson wrote:
For device assignment, we need to know when the VM writes an end
of interrupt to the APIC, which allows us to re-enable interrupts
on the physical device. Add a new wrapper for ioapic generated
interrupts with a callback on eoi and create an interfa
With the KVM irqchip, we need to get the EOI via an eventfd. This
adds support for that, abstracting the details to the caller.
The get_fd function allows drivers to make further optimizations
in handling the EOI. For instance with VFIO, we can make use of
an irqfd-like mechanism to have the VFI
For device assignment, we need to know when the VM writes an end
of interrupt to the APIC, which allows us to re-enable interrupts
on the physical device. Add a new wrapper for ioapic generated
interrupts with a callback on eoi and create an interface for
drivers to be notified on eoi.
Signed-off
Register the actual VM RAM using the new API
Signed-off-by: Alex Williamson
---
hw/pc.c | 12 ++--
1 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/hw/pc.c b/hw/pc.c
index 69b13bf..0ea6d10 100644
--- a/hw/pc.c
+++ b/hw/pc.c
@@ -912,14 +912,14 @@ void pc_memory_init(ram_a
Required for regions mapped via qemu_ram_alloc_from_ptr(). VFIO
will make use of this to remove mappings when devices are hot
unplugged. (Current callers of qemu_ram_alloc_from_ptr() should
probably need this too)
Signed-off-by: Alex Williamson
---
cpu-common.h |1 +
exec.c | 13 +
* Markus Armbruster [2010-10-29 11:11]:
> Ryan Harper writes:
>
> > * Markus Armbruster [2010-10-29 09:13]:
> >> [Note cc: Michael]
> >>
> >> Ryan Harper writes:
> >>
> >>
> >> If I understand your patch correctly, the difference between your
> >> drive_unplug and my blockdev_del is as foll
For VFIO based device assignment, we need to know what guest memory
areas are actual RAM. RAMBlocks have long since become a grab bag
of misc allocations, so aren't effective for this. Anthony has had
a RAM API in mind for a while now that addresses this problem. This
implements just enough of i
This adds a minimum chunk of Anthony's RAM API support so that we
can identify actual VM RAM versus all the other things that make
use of qemu_ram_alloc.
Signed-off-by: Alex Williamson
---
Makefile.target |1 +
cpu-common.h|2 +
memory.c| 82 +++
Ryan Harper writes:
> * Markus Armbruster [2010-10-29 09:13]:
>> [Note cc: Michael]
>>
>> Ryan Harper writes:
>>
>> > This patch series decouples the detachment of a block device from the
>> > removal
>> > of the backing pci-device. Removal of a hotplugged pci device requires the
>> > guest
Am 29.10.2010 17:28, schrieb Anthony Liguori:
> On 10/29/2010 09:57 AM, Kevin Wolf wrote:
>> Am 29.10.2010 16:40, schrieb Anthony Liguori:
>>
>>> On 10/29/2010 09:29 AM, Kevin Wolf wrote:
>>>
Am 29.10.2010 16:15, schrieb Anthony Liguori:
> I don't think it's a bad id
Anthony Liguori writes:
> On 10/29/2010 09:01 AM, Markus Armbruster wrote:
>> Ryan Harper writes:
>>
>>
>>> Block hot unplug is racy since the guest is required to acknowlege the ACPI
>>> unplug event; this may not happen synchronously with the device removal
>>> command
>>>
>>> This series
On 10/29/2010 09:57 AM, Kevin Wolf wrote:
Am 29.10.2010 16:40, schrieb Anthony Liguori:
On 10/29/2010 09:29 AM, Kevin Wolf wrote:
Am 29.10.2010 16:15, schrieb Anthony Liguori:
I don't think it's a bad idea to do that but to the extent that the
block API is designed after posi
For device assignment, we need to be able to retreive the IRQ that
the device interrupt pin is assigned to and be notified if that
mapping changes (this happens via ACPI interrupt link updates on
x86). We can then make use of the IRQ for EOI notification.
Current qemu-kvm device assignment code in
* Markus Armbruster [2010-10-29 09:13]:
> [Note cc: Michael]
>
> Ryan Harper writes:
>
> > This patch series decouples the detachment of a block device from the
> > removal
> > of the backing pci-device. Removal of a hotplugged pci device requires the
> > guest to respond before qemu tears do
Running programs that create large numbers of threads, such as this
snippet from libstdc++'s pthread7-rope.cc:
const int max_thread_count = 4;
const int max_loop_count = 1;
...
for (int j = 0; j < max_loop_count; j++)
{
...
for (int i = 0; i < max_thread_count; i++)
Am 29.10.2010 16:40, schrieb Anthony Liguori:
> On 10/29/2010 09:29 AM, Kevin Wolf wrote:
>> Am 29.10.2010 16:15, schrieb Anthony Liguori:
>>> I don't think it's a bad idea to do that but to the extent that the
>>> block API is designed after posix file I/O, close does not usually imply
>>> flush.
The translation of dmt/emt/dvpe/evpe was doing the moral equivalent of:
int x;
... /* no initialization of x */
x = f (x);
which confused later bits of TCG rather badly, leading to crashes.
Fix the helpers to only return results (those instructions have no
inputs), and fix the tr
On 10/29/2010 09:29 AM, Kevin Wolf wrote:
Am 29.10.2010 16:15, schrieb Anthony Liguori:
On 10/29/2010 09:01 AM, Markus Armbruster wrote:
Ryan Harper writes:
diff --git a/block.c b/block.c
index a19374d..be47655 100644
--- a/block.c
+++ b/block.c
@@ -1328,6 +1328,13 @@ void
Am 29.10.2010 16:15, schrieb Anthony Liguori:
> On 10/29/2010 09:01 AM, Markus Armbruster wrote:
>> Ryan Harper writes:
>>> diff --git a/block.c b/block.c
>>> index a19374d..be47655 100644
>>> --- a/block.c
>>> +++ b/block.c
>>> @@ -1328,6 +1328,13 @@ void bdrv_set_removable(BlockDriverState *bs,
This driver handles in-memory chardev operations. That's, all writes
to this driver are stored in an internal buffer and it doesn't talk
to the external world in any way.
Right now it's very simple: it supports only writes. But it can be
easily extended to support more operations.
This is going t
This command allows QMP clients to execute HMP commands.
Please, check the documentation added to the qmp-commands.hx file
for additional details about the interface and its limitations.
Signed-off-by: Luiz Capitulino
---
monitor.c | 42 ++
qmp-co
In which qmp-shell will exclusively use the HMP passthrough feature,
this is useful for testing.
Example:
(QEMU) info network
VLAN 0 devices:
user.0: net=10.0.2.0, restricted=n
e1000.0: model=e1000,macaddr=52:54:00:12:34:56
Devices not on any VLAN:
(QEMU)
Signed
This commit updates the qmp-shell script to use the new interface
introduced by the last commit.
Additionally, the following fixes/features are also introduced:
o TCP sockets support
o Update/add documentation
o Simple command-line completion
o Fix a number of unhandled errors
Signed-off-by:
It's broken and not really useful, let's just drop it.
Signed-off-by: Luiz Capitulino
---
QMP/README |5 +
QMP/vm-info | 33 -
2 files changed, 1 insertions(+), 37 deletions(-)
delete mode 100755 QMP/vm-info
diff --git a/QMP/README b/QMP/README
index
Simple example:
-> { "execute": "hmp_passthrough", "arguments": { "command-line": "print /i
10+25" } }
<- { "return": "35\r\n" }
Please, check individual patches for details. Also note that this series
depends on the script improvements one.
Thanks.
This commit simplifies and fixes a number of problems in the Python
QEMUMonitorProtocol example class.
It's almost a rewrite and it DOES BREAK the qmp-shell script (which
is going to be fixed in the next commit).
However, I'm not going to split this in different commits because it
could get up to
Please, check individual patches for details.
Thanks.
[Note cc: Michael]
Ryan Harper writes:
> This patch series decouples the detachment of a block device from the removal
> of the backing pci-device. Removal of a hotplugged pci device requires the
> guest to respond before qemu tears down the block device. In some cases, the
> guest may not resp
On 10/29/2010 09:01 AM, Markus Armbruster wrote:
Ryan Harper writes:
Block hot unplug is racy since the guest is required to acknowlege the ACPI
unplug event; this may not happen synchronously with the device removal command
This series aims to close a gap where by mgmt applications that
Ryan Harper writes:
> Block hot unplug is racy since the guest is required to acknowlege the ACPI
> unplug event; this may not happen synchronously with the device removal
> command
>
> This series aims to close a gap where by mgmt applications that assume the
> block resource has been removed w
Ryan Harper writes:
> Add a function to find a drive by id string.
>
> Changes since v1:
> -Coding Style fix
Recommend to put patch history below the --- line, so it doesn't get
included in the commit message.
> Signed-off-by: Ryan Harper
> ---
> blockdev.c | 13 +
> blockdev.h
Hi,
These patches improve the pulseaudio driver's buffer handling.
Separated from the win7 sound patch series, it is completely
independant stuff. Except maybe for the fact that the usb-audio
driver magnifies the pulseaudio buffering issues.
Fengguang, can you please have a look?
malc wants yo
On 10/29/2010 06:18 AM, Rusty Russell wrote:
Fixed - updated patch tested and attached.
OK. FWIW, I think this is an awesome idea.
Paravirtual OpenGL or the actual proposed implementation? Have you
looked at the actual code?
If I understand correctly, the implementation is an RPC of
Zap unused divisor field.
Raise the buffer size default.
Signed-off-by: Gerd Hoffmann
---
audio/paaudio.c | 10 +-
1 files changed, 1 insertions(+), 9 deletions(-)
diff --git a/audio/paaudio.c b/audio/paaudio.c
index 61af0c5..34bde23 100644
--- a/audio/paaudio.c
+++ b/audio/paaudio.c
Request reasonable buffer sizes from pulseaudio. Without this
pa_simple_write() can block quite long and lead to dropouts,
especially with guests which use small audio ring buffers.
Signed-off-by: Gerd Hoffmann
---
audio/paaudio.c | 12 +++-
1 files changed, 11 insertions(+), 1 deleti
Limit the size of data pieces processed by the pulseaudio worker
threads. Never ever process more than 1/4 of the buffer at once.
Background: The buffer area currently processed by the pulseaudio thread
is blocked, i.e. the main thread (or iothread) can't fill in more data
there. The buffer proc
Yes, I think so.
On Fri, Oct 29, 2010 at 4:16 PM, Michael S. Tsirkin wrote:
> On Thu, Oct 28, 2010 at 04:31:33PM +0800, chen huacai wrote:
>> Please see bonito64_pcibios_config_access() in
>> arch/mips/pci/ops-bonito64.c of Linux kernel code.
>> You will find something useful.
>
>
> Thanks!
> I f
Kevin Wolf writes:
> Am 21.10.2010 23:37, schrieb Ryan Harper:
>> * Daniel P. Berrange [2010-10-21 08:29]:
>>> On Tue, Oct 19, 2010 at 09:32:29AM -0500, Ryan Harper wrote:
Block hot unplug is racy since the guest is required to acknowlege the ACPI
unplug event; this may not happen sync
On Friday 29 October 2010 07:18:00 Rusty Russell wrote:
> On Wed, 27 Oct 2010 11:30:31 pm Ian Molton wrote:
> > On 19/10/10 11:39, Avi Kivity wrote:
> > > On 10/19/2010 12:31 PM, Ian Molton wrote:
> >
> > >>> 2. should start with a patch to the virtio-pci spec to document what
> > >>> you're doing
On Wed, 27 Oct 2010 11:30:31 pm Ian Molton wrote:
> On 19/10/10 11:39, Avi Kivity wrote:
> > On 10/19/2010 12:31 PM, Ian Molton wrote:
>
> >>> 2. should start with a patch to the virtio-pci spec to document what
> >>> you're doing
> >>
> >> Where can I find that spec?
> >
> > http://ozlabs.org/~ru
On Fri, Oct 29, 2010 at 11:54:27AM +0200, Markus Armbruster wrote:
> [Note cc: Michael & Gerd]
>
> Isaku Yamahata writes:
>
> > On Fri, Oct 29, 2010 at 10:02:47AM +0200, Markus Armbruster wrote:
> >> Isaku Yamahata writes:
> >>
> >> > On Thu, Oct 28, 2010 at 03:37:27AM -0700, Wei Xu wrote:
> >
[Note cc: Michael & Gerd]
Isaku Yamahata writes:
> On Fri, Oct 29, 2010 at 10:02:47AM +0200, Markus Armbruster wrote:
>> Isaku Yamahata writes:
>>
>> > On Thu, Oct 28, 2010 at 03:37:27AM -0700, Wei Xu wrote:
>> >> Isaku,
>> >>
>> >> To make things clear, let me rephrase the problem. With q35/
On Fri, Oct 29, 2010 at 10:02:47AM +0200, Markus Armbruster wrote:
> Isaku Yamahata writes:
>
> > On Thu, Oct 28, 2010 at 03:37:27AM -0700, Wei Xu wrote:
> >> Isaku,
> >>
> >> To make things clear, let me rephrase the problem. With q35/vPCIe, in VMM
> >> monitor, we can do hotplug like:
> >> pc
On Fri, Oct 29, 2010 at 8:25 AM, Kevin Wolf wrote:
> SCSI disks currently only support werror for write requests. This series adds
> rerror for failed read requests and respects werror also for flushes.
>
> v2:
> - Addressed Stefan's comments on patch 1/4
Looks good.
Stefan
On Fri, Oct 29, 2010 at 8:25 AM, Kevin Wolf wrote:
> This implements the rerror option for SCSI disks.
>
> It also includes minor changes to the write path where the same code is used
> that was criticized in the review for the changes to the read path required
> for
> rerror support.
>
> Signed-
On Thu, Oct 28, 2010 at 04:31:33PM +0800, chen huacai wrote:
> Please see bonito64_pcibios_config_access() in
> arch/mips/pci/ops-bonito64.c of Linux kernel code.
> You will find something useful.
Thanks!
I found this:
/* Clear aborts */
BONITO_PCICMD |= BONITO_PCICMD_MABORT_CLR
Isaku Yamahata writes:
> On Thu, Oct 28, 2010 at 03:37:27AM -0700, Wei Xu wrote:
>> Isaku,
>>
>> To make things clear, let me rephrase the problem. With q35/vPCIe, in VMM
>> monitor, we can do hotplug like:
>> pci_add auto| nic|storage
>> to hotplug a device to PCIe/PCI bus.
>>
>> But we have
This changes bdrv_flush to return 0 on success and -errno in case of failure.
It's a requirement for implementing proper error handle in users of bdrv_flush.
Signed-off-by: Kevin Wolf
Reviewed-by: Stefan Hajnoczi
---
block.c | 21 +
block.h |2 +-
b
This pulls the request completion for error cases from the caller to
scsi_disk_emulate_command. This should not change semantics, but allows to
reuse scsi_handle_write_error() for flushes in the next patch.
Signed-off-by: Kevin Wolf
Reviewed-by: Stefan Hajnoczi
---
hw/scsi-disk.c | 21 +++
Signed-off-by: Kevin Wolf
Reviewed-by: Stefan Hajnoczi
---
hw/scsi-disk.c | 17 -
1 files changed, 16 insertions(+), 1 deletions(-)
diff --git a/hw/scsi-disk.c b/hw/scsi-disk.c
index 96acfe3..6815239 100644
--- a/hw/scsi-disk.c
+++ b/hw/scsi-disk.c
@@ -45,6 +45,7 @@ do { fprin
SCSI disks currently only support werror for write requests. This series adds
rerror for failed read requests and respects werror also for flushes.
v2:
- Addressed Stefan's comments on patch 1/4
Kevin Wolf (4):
scsi-disk: Implement rerror option
block: Allow bdrv_flush to return errors
scsi
This implements the rerror option for SCSI disks.
It also includes minor changes to the write path where the same code is used
that was criticized in the review for the changes to the read path required for
rerror support.
Signed-off-by: Kevin Wolf
---
blockdev.c |6 ++--
hw/scsi-disk.c
Am 29.10.2010 04:41, Zhiyuan Shao wrote:
> On Thu, 2010-10-28 at 14:36 +0200, Jan Kiszka wrote:
>> Am 26.10.2010 14:22, Zhiyuan Shao wrote:
>>> Hi team,
>>>
>>> I am a Qemu User, and using Qemu 0.13.0 to debugging the linux kernel
>>> code (Qemu+GDB).
>>>
>>> During the usage, I found the Qemu deb
60 matches
Mail list logo
