Am 15.06.2012 22:47, schrieb Supriya Kannery:
> Struct BDRVReopenState along with three reopen related functions
> introduced for handling reopening of images safely. This can be
> extended by each of the block drivers to reopen respective
> image files.
>
> Signed-off-by: Supriya Kannery
>
> In
On 07/09/2012 10:05 AM, Luiz Capitulino wrote:
On Thu, 05 Jul 2012 11:06:56 -0400
Corey Bryant wrote:
On 07/04/2012 04:09 AM, Kevin Wolf wrote:
Am 03.07.2012 20:21, schrieb Corey Bryant:
On 07/03/2012 02:00 PM, Eric Blake wrote:
On 07/03/2012 11:46 AM, Corey Bryant wrote:
Yes, I thin
From: Pavel Hrdina
After rewrite DSKCHG bit handling the test has to be updated. Now
is needed to seek to different track to clear DSKCHG bit.
Signed-off-by: Pavel Hrdina
Signed-off-by: Kevin Wolf
---
tests/fdc-test.c | 25 +
1 files changed, 17 insertions(+), 8 dele
On 07/09/2012 09:16 AM, Kevin Wolf wrote:
From: Markus Armbruster
Commit 5bbdbb46 moved it to block.c because "other geometry guessing
functions already reside in block.c". Device-specific functionality
should be kept in device code, not the block layer. Move it back.
Disk geometry guessing i
From: MORITA Kazutaka
outstanding_list_head is used for both pending and inflight requests.
This patch splits it and improves readability.
Signed-off-by: MORITA Kazutaka
Signed-off-by: Kevin Wolf
---
block/sheepdog.c | 49 -
1 files changed, 2
From: MORITA Kazutaka
This patch increments the pending counter before sending requests, and
make sures that aiocb is not freed while sending them.
Signed-off-by: MORITA Kazutaka
Signed-off-by: Kevin Wolf
---
block/sheepdog.c | 29 -
1 files changed, 16 insertion
From: Markus Armbruster
Each test litters /tmp with several files: a pid file and two
sockets. Tidy up.
Signed-off-by: Markus Armbruster
Signed-off-by: Kevin Wolf
---
tests/libqtest.c | 29 -
1 files changed, 16 insertions(+), 13 deletions(-)
diff --git a/tests
Let the text console cursor blink at 2 HZ.
Signed-off-by: Jan Kiszka
---
Changes in v2:
- fixed semantic of CONSOLE_CURSOR_PERIOD and reduced frequency
I know there was a concern regarding the approach in general, but I
still consider it useful and visually more attractive than the static
curs
Am 15.06.2012 22:47, schrieb Supriya Kannery:
> New command "block_set_hostcache" added for dynamically changing
> host pagecache setting of a block device.
>
> Usage:
> block_set_hostcache
> = block device
> = on/off
>
> Example:
> (qemu) block_set_hostcache ide0-hd0 off
>
> Sign
Am 15.06.2012 22:47, schrieb Supriya Kannery:
> New error classes defined for hostcache setting and data
> sync error
>
> Signed-off-by: Supriya Kannery
>
> ---
> qerror.c |8
> qerror.h |6 ++
> 2 files changed, 14 insertions(+)
>
> Index: qemu/qerror.c
> ===
From: Markus Armbruster
Commit 5bbdbb46 moved it to block.c because "other geometry guessing
functions already reside in block.c". Device-specific functionality
should be kept in device code, not the block layer. Move it back.
Disk geometry guessing is still in block.c. To be moved out in a
l
Am 15.06.2012 23:07, schrieb Eric Blake:
> On 06/15/2012 02:47 PM, Supriya Kannery wrote:
>> Enhance "info block" to display hostcache setting for each
>> block device.
>>
>
>> ##
>> { 'type': 'BlockInfo',
>>'data': {'device': 'str', 'type': 'str', 'removable': 'bool',
>> - 'locked
From: Paolo Bonzini
The new function can be made a bit nicer than bdrv_append. It swaps the
whole contents, and then swaps back (using the usual t=a;a=b;b=t idiom)
the fields that need to stay on top. Thus, it does not need explicit
bdrv_detach_dev, bdrv_iostatus_disable, etc.
Signed-off-by: P
KVM performs TPR raising asynchronously to QEMU, specifically outside
QEMU's global lock. When an interrupt is injected into the APIC and TPR
is checked to decide if this can be delivered, a stale TPR value may be
used, causing spurious interrupts in the end.
Fix this by deferring apic_update_irq
When the guest modifies the LVT_LINT0 register, we need to check if some
pending PIC interrupt can now be delivered.
Signed-off-by: Jan Kiszka
---
hw/apic.c | 18 ++
1 files changed, 14 insertions(+), 4 deletions(-)
diff --git a/hw/apic.c b/hw/apic.c
index e65a35f..5b8f3e8 100
Commit d96e173769 refactored the reinjection of pending PIC interrupts.
However, it missed the potential loop of apic_update_irq ->
apic_deliver_pic_intr -> apic_local_deliver -> apic_set_irq ->
apic_update_irq that /could/ occur if LINT0 is injected as APIC_DM_FIXED
and that vector is currently bl
As Avi noted recently, there is a problem in way we inject interrupts
into the userspace APIC under KVM: The TRP check over the iothread may
race with the VCPU raising the TPR value while in KVM mode. Patch 3
addresses this issue.
The other two patches fix problems I came across while thinking abo
From: Paolo Bonzini
This is required when using blkdebug with raw format. Unlike qcow2/QED,
raw asks blkdebug for the length of the file, it doesn't get it from
a header.
Signed-off-by: Paolo Bonzini
Signed-off-by: Kevin Wolf
---
block/blkdebug.c |6 ++
1 files changed, 6 insertions(
Am 09.07.2012 15:26, schrieb Peter Maydell:
> On 9 July 2012 14:19, Andreas Färber wrote:
>> Am 25.06.2012 16:55, schrieb Peter Maydell:
>>> In our disassembly code, the bfd_vma type is always 64 bits,
>>> even if the target's virtual address width is only 32 bits. This
>>> means that when we prin
On 09.07.2012, at 16:36, Scott Wood wrote:
> On 07/09/2012 09:07 AM, Andreas Färber wrote:
>> Am 09.07.2012 16:04, schrieb Scott Wood:
>>> Recent patches "PPC: e500: rename mpc8544ds into generic file", "PPC:
>>> e500: split mpc8544ds machine from generic e500 code", and "PPC: e500:
>>> add gener
On 07/07/2012 08:37 AM, Michael Tokarev wrote:
I come across a patch in ububtu qemu-kvm package, this:
From: Nelson Elhage
Date: Thu, 19 May 2011 13:23:17 -0400
Subject: [PATCH] virtqueue: Sanity-check the length of indirect descriptors.
We were previously allowing arbitrarily-long descriptors,
On Mon, Jul 09, 2012 at 04:54:08PM +0800, Wenchao Xia wrote:
> Hi, Paolo and folks,
> qemu have good capabilities to access different virtual disks, I want
> to expose its block layer API to let 3rd party program linked in, such
> as management stack or block tools, to access images data directly
From: Paolo Bonzini
Signed-off-by: Paolo Bonzini
Signed-off-by: Kevin Wolf
---
block/raw.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/block/raw.c b/block/raw.c
index 09d9b48..ff34ea4 100644
--- a/block/raw.c
+++ b/block/raw.c
@@ -12,12 +12,14 @@ static int raw_op
Only buffers that map to unallocated blocks need to be zeroed.
Signed-off-by: Christoph Hellwig
---
block/sheepdog.c | 37 ++---
1 file changed, 18 insertions(+), 19 deletions(-)
Index: qemu/block/sheepdog.c
From: Pavel Hrdina
If you call the SENSE INTERRUPT STATUS command while there is no interrupt
waiting you get as result unknown command.
Fixed status0 register handling for read/write/format commands.
Signed-off-by: Pavel Hrdina
Signed-off-by: Kevin Wolf
---
hw/fdc.c | 34 +
The qemu_chr_new() function doesn't set errno on failure, so
don't print strerror(errno) on the error handling path when
dealing with the -serial, -parallel and -virtioconsole arguments.
This avoids nonsensical error messages like:
$ ./arm-softmmu/qemu-system-arm -serial wombat
qemu: could not
Add a missing guard that meant we would segfault if the guest read
UARTDR on a PL011 serial device which had no chr backend connected.
(This didn't happen for Linux guests because Linux reads the flags
register and doesn't try to read the UART if it's empty.)
Reported-by: Christian Müller
Signed-
Am 04.07.2012 18:41, schrieb MORITA Kazutaka:
> This reduces some code duplication.
>
> Signed-off-by: MORITA Kazutaka
Thanks, applied to the block branch.
Kevin
From: Pavel Hrdina
This bit is cleared on every successful seek to a different track (cylinder).
The seek is also called on revalidate or on read/write/format commands which
also clear the DSKCHG bit.
Signed-off-by: Pavel Hrdina
Signed-off-by: Kevin Wolf
---
hw/fdc.c | 79 ++
From: MORITA Kazutaka
Currently, no one reenters the yielded coroutine. This fixes it.
Signed-off-by: MORITA Kazutaka
Signed-off-by: Kevin Wolf
---
block/sheepdog.c | 14 ++
1 files changed, 14 insertions(+), 0 deletions(-)
diff --git a/block/sheepdog.c b/block/sheepdog.c
inde
From: MORITA Kazutaka
This fixes warnings about dprintf format in debug mode.
Signed-off-by: MORITA Kazutaka
Signed-off-by: Kevin Wolf
---
block/sheepdog.c |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/block/sheepdog.c b/block/sheepdog.c
index 8877f45..afd06a
The following changes since commit 84988cf910a6881f2180fdcec516b60f8f0dc8c4:
bitops.h: Add functions to extract and deposit bitfields (2012-07-07 09:07:01
+)
are available in the git repository at:
git://repo.or.cz/qemu/kevin.git for-anthony
MORITA Kazutaka (6):
sheepdog: fix dpr
Am 09.07.2012 16:04, schrieb Scott Wood:
> Recent patches "PPC: e500: rename mpc8544ds into generic file", "PPC:
> e500: split mpc8544ds machine from generic e500 code", and "PPC: e500:
> add generic e500 platform" moved certain e500-related files to the bottom
> of the makefile because they're now
[resend, forgot the v3, sorry]
This patch set implements support for a sane default CPU type, that plays the
middle ground between -cpu host (unmanagable test matrix) and -cpu qemu64
(breaks
assumptions wrt family/model numbers). It also makes it the default for -M pc,
so that users who don't spe
Am 06.07.2012 19:40, schrieb Corey Bryant:
>
>
> On 07/06/2012 05:11 AM, Kevin Wolf wrote:
>> Am 05.07.2012 19:00, schrieb Eric Blake:
>>> On 07/05/2012 10:35 AM, Corey Bryant wrote:
1. client calls 'add-fd', qemu is now tracking fd=4 in fdset1 with
refcount of 0; fd=4's in-use flag is
On Thu, 05 Jul 2012 11:06:56 -0400
Corey Bryant wrote:
>
>
> On 07/04/2012 04:09 AM, Kevin Wolf wrote:
> > Am 03.07.2012 20:21, schrieb Corey Bryant:
> >> On 07/03/2012 02:00 PM, Eric Blake wrote:
> >>> On 07/03/2012 11:46 AM, Corey Bryant wrote:
> >>>
>
> Yes, I think adding a +1 to
Recent patches "PPC: e500: rename mpc8544ds into generic file", "PPC:
e500: split mpc8544ds machine from generic e500 code", and "PPC: e500:
add generic e500 platform" moved certain e500-related files to the bottom
of the makefile because they're now in ppc/, but the dependency on
CONFIG_FDT was ac
We want all configure tests pass with -Werror if it is enabled. So we
need to update QEMU_CFLAGS early on to make sure we also pass it in to
all the compile test jobs.
This fixes a warning-became-error bug in nss for me with the default
configuration:
In file included from /usr/include/nss3/pkcs1
On 07/09/2012 07:48 AM, Alexander Graf wrote:
>
> On 09.07.2012, at 15:47, Eric Blake wrote:
>
>> On 07/09/2012 06:10 AM, Alexander Graf wrote:
>>
>>>
>>> This fixes a lot of subtle breakage in the GNU toolchain (libgmp) which
>>> hicks up on QEMU's non-existent CPU models.
>>
>> s/hicks up/hiccu
On 09.07.2012, at 15:47, Eric Blake wrote:
> On 07/09/2012 06:10 AM, Alexander Graf wrote:
>
>>
>> This fixes a lot of subtle breakage in the GNU toolchain (libgmp) which
>> hicks up on QEMU's non-existent CPU models.
>
> s/hicks up/hiccups/
>
>
>>
>> v2 -> v3:
>>
>> - fix typo in commit
On 07/09/2012 06:10 AM, Alexander Graf wrote:
>
> This fixes a lot of subtle breakage in the GNU toolchain (libgmp) which
> hicks up on QEMU's non-existent CPU models.
s/hicks up/hiccups/
>
> v2 -> v3:
>
> - fix typo in commit message
but not all of them :)
--
Eric Blake ebl...@redhat
During discussions on whether to support -cpu host in SLE, I found myself
disagreeing to the thought, because it potentially opens a big can of worms
for potential bugs. But if I already am so opposed to it for SLE, how can
it possibly be reasonable to default to -cpu host in upstream QEMU? And wha
On 07/09/12 14:23, Alexander Graf wrote:
> We want all configure tests pass with -Werror if it is enabled. So we
> need to update QEMU_CFLAGS early on to make sure we also pass it in to
> all the compile test jobs.
Much better than v1
Acked-by: Gerd Hoffmann
cheers,
Gerd
We want all configure tests pass with -Werror if it is enabled. So we
need to update QEMU_CFLAGS early on to make sure we also pass it in to
all the compile test jobs.
This fixes a warning-became-error bug in nss for me with the default
configuration:
In file included from /usr/include/nss3/pkcs1
During discussions on whether to support -cpu host in SLE, I found myself
disagreeing to the thought, because it potentially opens a big can of worms
for potential bugs. But if I already am so opposed to it for SLE, how can
it possibly be reasonable to default to -cpu host in upstream QEMU? And wha
When running QEMU without -cpu parameter, the user usually wants a sane
default. So far, we're using the qemu64/qemu32 CPU type, which basically
means "the maximum TCG can emulate".
That's a really good default when using TCG, but when running with KVM
we much rather want a default saying "the max
On 09.07.2012, at 15:29, Gerd Hoffmann wrote:
> On 07/09/12 14:06, Alexander Graf wrote:
>> When just calling ./configure on my box, I always ran into the same issue:
>>
>> In file included from /usr/include/nss3/pkcs11t.h:1780,
>> from /usr/include/nss3/keythi.h:41,
>>
On 07/09/12 14:06, Alexander Graf wrote:
> When just calling ./configure on my box, I always ran into the same issue:
>
> In file included from /usr/include/nss3/pkcs11t.h:1780,
> from /usr/include/nss3/keythi.h:41,
> from /usr/include/nss3/keyt.h:41,
>
The kvm_enabled() helper doesn't work in a function as early as -cpu ?
yet. It also doesn't make sense to list the -cpu ? output conditional on
the -enable-kvm parameter. So let's always mention -cpu host in the
CPU list when KVM is supported on that configuration.
In addition, this patch also add
Am 09.07.2012 14:06, schrieb Alexander Graf:
> When just calling ./configure on my box, I always ran into the same issue:
>
> In file included from /usr/include/nss3/pkcs11t.h:1780,
> from /usr/include/nss3/keythi.h:41,
> from /usr/include/nss3/keyt.h:41,
>
This patch set implements support for a sane default CPU type, that plays the
middle ground between -cpu host (unmanagable test matrix) and -cpu qemu64
(breaks
assumptions wrt family/model numbers). It also makes it the default for -M pc,
so that users who don't specify a specific CPU type on the
When running QEMU without -cpu parameter, the user usually wants a sane
default. So far, we're using the qemu64/qemu32 CPU type, which basically
means "the maximum TCG can emulate".
That's a really good default when using TCG, but when running with KVM
we much rather want a default saying "the max
On 9 July 2012 14:19, Andreas Färber wrote:
> Am 25.06.2012 16:55, schrieb Peter Maydell:
>> In our disassembly code, the bfd_vma type is always 64 bits,
>> even if the target's virtual address width is only 32 bits. This
>> means that when we print out addresses we need to truncate them
>> to 32
When just calling ./configure on my box, I always ran into the same issue:
In file included from /usr/include/nss3/pkcs11t.h:1780,
from /usr/include/nss3/keythi.h:41,
from /usr/include/nss3/keyt.h:41,
from /usr/include/nss3/pk11pub.h:43,
Hi Mike,
Am 09.07.2012 15:04, schrieb Mike Frysinger:
> The current bss clear logic assumes the target mmap address and host
> address are the same. Use g2h to translate from the target address
> space to the host so we can call memset on it.
>
> Signed-off-by: Mike Frysinger
> ---
> linux-use
Am 25.06.2012 16:55, schrieb Peter Maydell:
> In our disassembly code, the bfd_vma type is always 64 bits,
> even if the target's virtual address width is only 32 bits. This
> means that when we print out addresses we need to truncate them
> to 32 bits, to avoid odd output which has incorrectly sig
On 9 July 2012 14:04, Mike Frysinger wrote:
> The current bss clear logic assumes the target mmap address and host
> address are the same. Use g2h to translate from the target address
> space to the host so we can call memset on it.
>
> Signed-off-by: Mike Frysinger
Reviewed-by: Peter Maydell
The current bss clear logic assumes the target mmap address and host
address are the same. Use g2h to translate from the target address
space to the host so we can call memset on it.
Signed-off-by: Mike Frysinger
---
linux-user/flatload.c |2 +-
1 files changed, 1 insertions(+), 1 deletions
On 9 July 2012 13:45, Andreas Färber wrote:
> Am 09.07.2012 12:27, schrieb Peter Maydell:
>> On 25 June 2012 15:55, Peter Maydell wrote:
>>> In our disassembly code, the bfd_vma type is always 64 bits,
>>> even if the target's virtual address width is only 32 bits. This
>>> means that when we pri
Eric Blake writes:
> On 07/09/2012 06:10 AM, Peter Maydell wrote:
>> On 9 July 2012 13:07, Eric Blake wrote:
>>> That is, we are filtering based on the explicit presence of a literal
>>> '?' in the help output to determine whether we can further filter based
>>> on '-device device,?' queries wit
Am 09.07.2012 12:59, schrieb igor:
> On 06/20/2012 03:35 PM, Andreas Färber wrote:
>> Am 20.06.2012 14:59, schrieb Igor Mammedov:
>>> It's not correct to make CPU runnable (i.e. calling x86_cpu_realize())
>>> when not all properties are set (APIC in this case).
>>>
>>> Fix it by calling x86_cpu_rea
This seems to be fixed in Fedora rawhide packages. Works for me now
with:
This issue seems to be fixed in current rawhide packages:
qemu-common.x86_64 2:1.1.0-4.fc18
qemu-img.x86_64 2:1.1.0-4.fc18
qemu-kv
Am 09.07.2012 12:27, schrieb Peter Maydell:
> Ping? [patchwork url http://patchwork.ozlabs.org/patch/167132/]
>
> -- PMM
>
> On 25 June 2012 15:55, Peter Maydell wrote:
>> In our disassembly code, the bfd_vma type is always 64 bits,
>> even if the target's virtual address width is only 32 bits.
Proposed patch that would allow '-cpu help' &co:
http://patchwork.ozlabs.org/patch/169798/
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1022331
Title:
-cpu ? causes confusion when directory has 1-
On Mon, Jul 09, 2012 at 06:07:48AM -0600, Eric Blake wrote:
> On 07/09/2012 05:52 AM, Peter Maydell wrote:
> > For command line options which permit '?' meaning 'please list the
> > permitted values', add support for 'help' as a synonym, by abstracting
> > the check out into a helper function.
> >
On 07/09/12 12:45, Paolo Bonzini wrote:
> Il 09/07/2012 12:39, Gerd Hoffmann ha scritto:
>> On 07/09/12 12:33, Gerd Hoffmann wrote:
>>> Hi,
>>>
>>> v2 of the usb attached scsi emulation patches. Patch #1 is almost
>>> unmodified compared to v1. Patch #2 is new and makes UAS emulation
>>> use th
On 07/09/2012 06:10 AM, Peter Maydell wrote:
> On 9 July 2012 13:07, Eric Blake wrote:
>> That is, we are filtering based on the explicit presence of a literal
>> '?' in the help output to determine whether we can further filter based
>> on '-device device,?' queries without confusing qemu or libv
Am 09.07.2012 12:19, schrieb Fabien Chouteau:
> Any comment?
>
> On 07/04/2012 01:04 PM, Fabien Chouteau wrote:
>> The goal is to make ctrl-a x to close Qemu in a clean way. The current
>> exit(0) skips a lot of cleanup/close functions, for example in block
>> drivers.
>>
>> Signed-off-by: Fabien
On 9 July 2012 13:07, Eric Blake wrote:
> That is, we are filtering based on the explicit presence of a literal
> '?' in the help output to determine whether we can further filter based
> on '-device device,?' queries without confusing qemu or libvirt;
> changing the 'help' output means that old l
On 07/09/2012 05:52 AM, Peter Maydell wrote:
> For command line options which permit '?' meaning 'please list the
> permitted values', add support for 'help' as a synonym, by abstracting
> the check out into a helper function.
>
> Update the documentation to use 'help' rather than '?', since '?'
>
On 02.07.2012, at 16:25, Avi Kivity wrote:
> On 06/26/2012 07:39 PM, Alexander Graf wrote:
>> During discussions on whether to make -cpu host the default in SLE, I found
>> myself disagreeing to the thought, because it potentially opens a big can
>> of worms for potential bugs. But if I already a
For command line options which permit '?' meaning 'please list the
permitted values', add support for 'help' as a synonym, by abstracting
the check out into a helper function.
Update the documentation to use 'help' rather than '?', since '?'
is a shell metacharacter and thus prone to fail confusin
Replace iso transfer fprintf's with trace points. Also rename existing
tracepoints so they all match usb_host_iso_*.
Signed-off-by: Gerd Hoffmann
---
hw/usb/host-linux.c | 10 ++
trace-events|6 --
2 files changed, 10 insertions(+), 6 deletions(-)
diff --git a/hw/usb/
Hi,
Here comes the most recent usb patch queue, featuring a collection of
little bug fixes all over the place. See individual patches for
details.
please pull,
Gerd
The following changes since commit 84988cf910a6881f2180fdcec516b60f8f0dc8c4:
bitops.h: Add functions to extract and deposit
Il 09/07/2012 12:19, Fabien Chouteau ha scritto:
> Any comment?
Looks good to me. Blue, can you apply it while Anthony is on holiday?
Paolo
> On 07/04/2012 01:04 PM, Fabien Chouteau wrote:
>> The goal is to make ctrl-a x to close Qemu in a clean way. The current
>> exit(0) skips a lot of cleanu
Use ehci_flush_qh to make sure we touch inly the fields the hc is
allowed to touch.
Signed-off-by: Gerd Hoffmann
---
hw/usb/hcd-ehci.c | 37 ++---
1 files changed, 18 insertions(+), 19 deletions(-)
diff --git a/hw/usb/hcd-ehci.c b/hw/usb/hcd-ehci.c
index 1582c2
Signed-off-by: Hervé Poussineau
---
hw/esp.c |6 ++
trace-events |1 +
2 files changed, 7 insertions(+)
diff --git a/hw/esp.c b/hw/esp.c
index ac91f00..985a2ee 100644
--- a/hw/esp.c
+++ b/hw/esp.c
@@ -117,6 +117,7 @@ struct ESPState {
#define CMD_SELATN 0x42
#define CMD_SELA
Create a new usb_ep_reset() function to reset endpoint state, without
re-initialiting the queues, so we don't unlink in-flight packets just
because usb-host has to re-parse the descriptor tables.
Signed-off-by: Gerd Hoffmann
---
hw/usb.h|1 +
hw/usb/core.c | 13 ++
On 09.07.2012, at 13:19, Markus Armbruster wrote:
> Alexander Graf writes:
>
>> On 09.07.2012, at 13:06, Markus Armbruster wrote:
>>
>>> Kevin Wolf writes:
>>>
Am 09.07.2012 10:50, schrieb Markus Armbruster:
> Alexander Graf writes:
>
>> We've had support for creating AHCI
Signed-off-by: Hervé Poussineau
---
hw/esp.c |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/hw/esp.c b/hw/esp.c
index 85078e0..a1f5b8a 100644
--- a/hw/esp.c
+++ b/hw/esp.c
@@ -50,6 +50,7 @@ struct ESPState {
uint8_t wregs[ESP_REGS];
qemu_irq irq;
uint32_
Alexander Graf writes:
> On 09.07.2012, at 13:06, Markus Armbruster wrote:
>
>> Kevin Wolf writes:
>>
>>> Am 09.07.2012 10:50, schrieb Markus Armbruster:
Alexander Graf writes:
> We've had support for creating AHCI devices using -device for a while now,
> but it's cumbersome
From: Hans de Goede
Signed-off-by: Hans de Goede
Signed-off-by: Gerd Hoffmann
---
hw/usb/redirect.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/hw/usb/redirect.c b/hw/usb/redirect.c
index d949f04..10b4fbb 100644
--- a/hw/usb/redirect.c
+++ b/hw/usb/redirect.c
@@ -
Signed-off-by: Hervé Poussineau
---
hw/esp.c |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/hw/esp.c b/hw/esp.c
index a1f5b8a..d9dd2aa 100644
--- a/hw/esp.c
+++ b/hw/esp.c
@@ -186,7 +186,7 @@ static void esp_dma_enable(void *opaque, int irq, int level)
static v
On 09.07.2012, at 13:06, Markus Armbruster wrote:
> Kevin Wolf writes:
>
>> Am 09.07.2012 10:50, schrieb Markus Armbruster:
>>> Alexander Graf writes:
>>>
We've had support for creating AHCI devices using -device for a while now,
but it's cumbersome to users. We really should provid
Kevin Wolf writes:
> Am 09.07.2012 10:50, schrieb Markus Armbruster:
>> Alexander Graf writes:
>>
>>> We've had support for creating AHCI devices using -device for a while now,
>>> but it's cumbersome to users. We really should provide an easier way for
>>> them to leverage the power of AHCI!
>
Gerd Hoffmann writes:
> Hi,
>
>>> If -hda has the semantics of "create an IDE device", then no, we can't
>>> change it. It doesn't however. IIRC on -M pseries -hda creates SCSI
>>> devices. On s390 -hda creates virtio devices. So if on -M q35 -hda would
>>> create if=ahci, I don't see how th
From: Hans de Goede
Commit 0f588df8b3688b00e77aabaa32e26ece5f19bd39, added code
to ehci_wakeup to kick the async schedule on wakeup, but the else
was positioned wrong making it trigger for devices which are routed
to the companion rather then to the ehci controller itself.
This patch fixes this.
Signed-off-by: Hervé Poussineau
---
hw/esp.c |4
trace-events |1 +
2 files changed, 5 insertions(+)
diff --git a/hw/esp.c b/hw/esp.c
index 985a2ee..85078e0 100644
--- a/hw/esp.c
+++ b/hw/esp.c
@@ -113,6 +113,7 @@ struct ESPState {
#define CMD_MSGACC 0x12
#define CMD_PAD
On 06/20/2012 03:35 PM, Andreas Färber wrote:
Am 20.06.2012 14:59, schrieb Igor Mammedov:
It's not correct to make CPU runnable (i.e. calling x86_cpu_realize())
when not all properties are set (APIC in this case).
Fix it by calling x86_cpu_realize() at board level after APIC is
initialized, rig
Signed-off-by: Hervé Poussineau
---
hw/esp.c | 162 --
1 file changed, 95 insertions(+), 67 deletions(-)
diff --git a/hw/esp.c b/hw/esp.c
index d9dd2aa..796cdc1 100644
--- a/hw/esp.c
+++ b/hw/esp.c
@@ -44,12 +44,9 @@
typedef struct E
Only write back the dwords the hc is supposed to update. Should not
make a difference in theory as the guest must not touch the td while
it is active to avoid races. But it is still more correct.
Signed-off-by: Gerd Hoffmann
---
hw/usb/hcd-ehci.c |6 --
1 files changed, 4 insertions(+)
From: Hans de Goede
hcd-ehci.c is missing an usb_packet_init() call for the ipacket UsbPacket
it uses for isoc transfers, triggering an assert (taking the entire vm down)
in usb_packet_setup as soon as any isoc transfers are done by a high speed
USB device.
Signed-off-by: Hans de Goede
Signed-o
Signed-off-by: Hervé Poussineau
---
hw/esp.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/hw/esp.c b/hw/esp.c
index 8d73e56..aff8de6 100644
--- a/hw/esp.c
+++ b/hw/esp.c
@@ -270,7 +270,7 @@ static void handle_satn(ESPState *s)
uint8_t buf[32];
int len;
Il 09/07/2012 12:39, Gerd Hoffmann ha scritto:
> On 07/09/12 12:33, Gerd Hoffmann wrote:
>> Hi,
>>
>> v2 of the usb attached scsi emulation patches. Patch #1 is almost
>> unmodified compared to v1. Patch #2 is new and makes UAS emulation
>> use the new free_request callback (patch just posted b
At 07/06/2012 07:09 PM, Jan Kiszka Wrote:
> On 2012-07-06 11:41, Wen Congyang wrote:
>> The action is the same as -onpanic parameter.
>
> As explained in patch 5, now that we have a related device, this no
> longer needs to be a machine property.
>
> Would could be a machine property is enabling/
On 07/09/12 12:33, Gerd Hoffmann wrote:
> Hi,
>
> v2 of the usb attached scsi emulation patches. Patch #1 is almost
> unmodified compared to v1. Patch #2 is new and makes UAS emulation
> use the new free_request callback (patch just posted by paolo) and
> obviously depends on that patch to com
zero is a valid interface number, so don't use it when resetting the
endpoints.
Signed-off-by: Gerd Hoffmann
---
hw/usb.h |2 ++
hw/usb/core.c |4 ++--
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/hw/usb.h b/hw/usb.h
index 9cd2f89..7ed8fb8 100644
--- a/hw/usb.h
+++
With the new free_request callback for SCSIBusInfo we can use scsi
request refcounting instead of our own for the uas request lifecycle.
Signed-off-by: Gerd Hoffmann
---
hw/usb/dev-uas.c | 33 ++---
1 files changed, 10 insertions(+), 23 deletions(-)
diff --git a/hw
$subject says all. First cut.
It's a pure UAS (usb attached scsi) emulation, without BOT (bulk-only
transport) compatibility. If your guest can't handle it use usb-storage
instead.
The emulation works like any other scsi hba emulation (eps, lsi, virtio,
megasas, ...). It provides just the HBA
Hi,
v2 of the usb attached scsi emulation patches. Patch #1 is almost
unmodified compared to v1. Patch #2 is new and makes UAS emulation
use the new free_request callback (patch just posted by paolo) and
obviously depends on that patch to compile.
cheers,
Gerd
Gerd Hoffmann (2):
usb: add
101 - 200 of 246 matches
Mail list logo
