On Mon, Jul 15, 2013 at 07:15:55PM +0200, Paolo Bonzini wrote:
> Il 15/07/2013 18:52, Anthony Liguori ha scritto:
> > Cornelia Huck writes:
> >
> >> The following changes since commit
> >> c3cb8e77804313e1be99b5f28a34a346736707a5:
> >>
> >> ioport: remove LITTLE_ENDIAN mark for portio (2013-07
On 15.07.2013 23:27, Eric Blake wrote:
On 07/15/2013 04:55 AM, Peter Lieven wrote:
this patch adds an efficient encoding for zero blocks by
adding a new flag indiciating a block is completly zero.
s/indiciating/indicating/
s/completly/completely/
additionally bdrv_write_zeros() is used at the
On 2013-07-14 17:18, Anthony Liguori wrote:
> On Sun, Jul 14, 2013 at 9:58 AM, Peter Maydell
> wrote:
>> On 14 July 2013 14:05, Anthony Liguori wrote:
Also, what devices exactly would have a non-native byte order?!? I'm
confused...
>>>
>>> MMIO/PIO requests don't have a byte order. I
Il 16/07/2013 08:47, Peter Lieven ha scritto:
>>
>> @@ -2977,7 +2977,11 @@ static int64_t coroutine_fn
>> bdrv_co_get_block_status(BlockDriverState *bs,
>> if (!bs->drv->bdrv_co_get_block_status) {
>> *pnum = nb_sectors;
>> -return BDRV_BLOCK_DATA;
>> +ret = BDRV_B
Paolo,
--On 16 July 2013 08:16:42 +0200 Paolo Bonzini wrote:
You did. But aio_wait() ignores the timeout. It is only used by the
main loop.
OK well that seems worth fixing in any case, as even without timed bh's
that means no bh can be executed for an indeterminate time. I'll have
a look a
Il 16/07/2013 09:30, Alex Bligh ha scritto:
>
>> You did. But aio_wait() ignores the timeout. It is only used by the
>> main loop.
>
> OK well that seems worth fixing in any case, as even without timed bh's
> that means no bh can be executed for an indeterminate time. I'll have
> a look at that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 16/07/2013 09:18, Jan Kiszka ha scritto:
> Sorry for sending out invitations and then being late to this party
> - vacation. What is the status now? Do we have a short-term plan to
> avoid the regression or is this better solved by cleaning up the
>
On 16.07.2013 09:19, Paolo Bonzini wrote:
Il 16/07/2013 08:47, Peter Lieven ha scritto:
@@ -2977,7 +2977,11 @@ static int64_t coroutine_fn
bdrv_co_get_block_status(BlockDriverState *bs,
if (!bs->drv->bdrv_co_get_block_status) {
*pnum = nb_sectors;
-return BDRV_BLOCK_D
On Tue, Jul 16, 2013 at 08:19:48AM +0200, Paolo Bonzini wrote:
> Il 16/07/2013 03:27, Hu Tao ha scritto:
> > > I think it's the same. One "-numa mem" option = one "-device dimm"
> > > option; both define one range. Unused memory ranges may remain if you
> > > stumble upon a unusable range such as
Am 12.07.2013 um 08:58 hat Bharata B Rao geschrieben:
> gluster: Use pkg-config to configure GlusterFS block driver
>
> Use pkg-config to determine the version and library dependency
> for GlusterFS block driver.
>
> Signed-off-by: Bharata B Rao
> ---
> configure | 20 +++-
>
Am 12.07.2013 um 09:00 hat Bharata B Rao geschrieben:
> gluster: Add discard support for GlusterFS block driver.
>
> Implement bdrv_aio_discard for gluster.
>
> Signed-off-by: Bharata B Rao
Reviewed-by: Kevin Wolf
Am 16.07.2013 um 08:20 schrieb Paolo Bonzini :
> Il 16/07/2013 07:19, Alexey Kardashevskiy ha scritto:
>> In the past, IO space could not be mapped into the memory address space
>> so we introduced a workaround for that. Nowadays it does not look
>> necessary so we can remove the workaround and
On 07/16/2013 03:06 AM, Peter Crosthwaite wrote:
+
+memory_region_init_io(&etsec->io_area, OBJECT(etsec), &etsec_ops,
etsec,
+ "eTSEC", 0x1000);
>>>
>>> Constant size memory_region_init_io should be migrated to the Object::Init
>>> fm.
>>>
>>
>> Wh
On 07/16/2013 06:32 PM, Alexander Graf wrote:
>
>
> Am 16.07.2013 um 08:20 schrieb Paolo Bonzini :
>
>> Il 16/07/2013 07:19, Alexey Kardashevskiy ha scritto:
>>> In the past, IO space could not be mapped into the memory address space
>>> so we introduced a workaround for that. Nowadays it does n
Am 16.07.2013 um 10:37 schrieb Alexey Kardashevskiy :
> On 07/16/2013 06:32 PM, Alexander Graf wrote:
>>
>>
>> Am 16.07.2013 um 08:20 schrieb Paolo Bonzini :
>>
>>> Il 16/07/2013 07:19, Alexey Kardashevskiy ha scritto:
In the past, IO space could not be mapped into the memory address spa
On Tue, 2013-07-16 at 10:32 +0200, Alexander Graf wrote:
> >> Did I miss anything here?
> >
> > No, I don't think so. The patch looks good.
>
> ... and will break all Mac targets again, no? Not to speak of non-ppc
> devices.
Do you know why it breaks ? Can you suggest what's wrong and how to fi
Hi, Gerd
My Qemu version is 1.5.1, and use libusb for usb pass through.
I pass through a host usb device to the guest by bus number and
physical port, when I unplug the usb device from
the host, and plug in on the same physical port immediately, but the usb device
don't show up i
On Tue, 16 Jul 2013 15:10:41 +0800
Stefan Hajnoczi wrote:
> On Mon, Jul 15, 2013 at 07:15:55PM +0200, Paolo Bonzini wrote:
> > Il 15/07/2013 18:52, Anthony Liguori ha scritto:
> > > Cornelia Huck writes:
> > >
> > >> The following changes since commit
> > >> c3cb8e77804313e1be99b5f28a34a346736
Am 11.07.2013 um 22:25 hat Eric Blake geschrieben:
> On 07/09/2013 03:53 AM, Kevin Wolf wrote:
>
> Worth repeating this comment from the code into the commit message?
>
> > + * qdict_flatten(): For each nested QDict with key x, all fields with
> key y
> > + * are moved to this QDict and their key
Am 16.07.2013 um 10:45 schrieb Benjamin Herrenschmidt
:
> On Tue, 2013-07-16 at 10:32 +0200, Alexander Graf wrote:
Did I miss anything here?
>>>
>>> No, I don't think so. The patch looks good.
>>
>> ... and will break all Mac targets again, no? Not to speak of non-ppc
>> devices.
>
> D
On 07/16/2013 07:01 PM, Alexander Graf wrote:
>
>
> Am 16.07.2013 um 10:45 schrieb Benjamin Herrenschmidt
> :
>
>> On Tue, 2013-07-16 at 10:32 +0200, Alexander Graf wrote:
> Did I miss anything here?
No, I don't think so. The patch looks good.
>>>
>>> ... and will break all Mac
Il 16/07/2013 10:54, Cornelia Huck ha scritto:
>> > Acked-by: Stefan Hajnoczi
>> >
> Thank you.
>
> Any further guidelines on when to ask for acks from you guys? The mode
> I've been operating in is mostly "if virtio-pci provides this feature,
> it shouldn't be half bad and we want it in virtio-
Il 16/07/2013 09:54, Peter Lieven ha scritto:
> On 16.07.2013 09:19, Paolo Bonzini wrote:
>> Il 16/07/2013 08:47, Peter Lieven ha scritto:
@@ -2977,7 +2977,11 @@ static int64_t coroutine_fn
bdrv_co_get_block_status(BlockDriverState *bs,
if (!bs->drv->bdrv_co_get_block_status
Signed-off-by: Alexey Kardashevskiy
---
target-ppc/kvm.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/target-ppc/kvm.c b/target-ppc/kvm.c
index 61f2737..606bdb9 100644
--- a/target-ppc/kvm.c
+++ b/target-ppc/kvm.c
@@ -1628,7 +1628,7 @@ void *kvmppc_create_spapr_tce(uint
On 07/16/2013 01:11 AM, Anthony Liguori wrote:
> This series is based on Alexey's series:
>
> spapr: migration, pci, msi, power8
>
> Which in turn was based on work by David Gibson.
>
> I've removed the bits not related to migration and made the
> following changes:
>
> 1) QOMify TCE tables
On Tue, 16 Jul 2013 08:19:48 +0200
Paolo Bonzini wrote:
> Il 16/07/2013 03:27, Hu Tao ha scritto:
> > > I think it's the same. One "-numa mem" option = one "-device dimm"
> > > option; both define one range. Unused memory ranges may remain if you
> > > stumble upon a unusable range such as the
On Tue, 16 Jul 2013 15:27:19 +0800
Hu Tao wrote:
> On Tue, Jul 16, 2013 at 08:19:48AM +0200, Paolo Bonzini wrote:
> > Il 16/07/2013 03:27, Hu Tao ha scritto:
> > > > I think it's the same. One "-numa mem" option = one "-device dimm"
> > > > option; both define one range. Unused memory ranges ma
Il 16/07/2013 12:19, Igor Mammedov ha scritto:
> On Tue, 16 Jul 2013 08:19:48 +0200
> Paolo Bonzini wrote:
>
>> Il 16/07/2013 03:27, Hu Tao ha scritto:
I think it's the same. One "-numa mem" option = one "-device dimm"
option; both define one range. Unused memory ranges may remain if
This is an implement of qmp full-introspection,
parse and convert the json string to a dynamical tree,
return it to management through QMP command output.
Anthony has another suggestion:
http://lists.nongnu.org/archive/html/qemu-devel/2013-07/msg01903.html
The whole output of query-qmp-schema c
Introduces new monitor command to query QMP schema information,
the return data is a dynamical and nested dict/list, it contains
the useful metadata to help management to check feature support,
QMP commands detail, etc.
I added a document for QMP introspection support.
(docs/qmp-full-introspection
QMP schema is defined in a json file, it will be parsed by
qapi scripts and generate C files.
We want to return the schema information to management,
this patch converts the json file to a string table in a
C head file, then we can use the json content.
eg:
const char *const qmp_schema_table[]
Il 16/07/2013 12:37, Amos Kong ha scritto:
> So here I defined a 'DataObject' type in qapi-schema.json,
> it's used to describe the dynamical dictionary/list/string.
>
> { 'type': 'DataObject',
> 'data': { '*key': 'str', '*type': 'str', '*data': ['DataObject'] } }
This is missing '*optional': '
On Mon, Jul 15, 2013 at 09:28:28PM +0300, Michael S. Tsirkin wrote:
> On Thu, Jul 11, 2013 at 10:28:15PM +0800, Amos Kong wrote:
> > Markus added some comments on old patchset, this patch contains
> > some additional fixes, it's based on MST's PCI tree.
> >
> > * Fix typos (missed 1.6, NIC)
> > *
On Tue, Jul 02, 2013 at 10:20:39AM -0400, Luiz Capitulino wrote:
> On Tue, 2 Jul 2013 16:37:29 +0800
> Amos Kong wrote:
>
> > > Btw, I find your approach interesting but I'm wondering if it's going to
> > > be a good thing to keep all the schema in memory. Do you have an idea
> > > on its size?
>
Il 15/07/2013 12:49, Peter Lieven ha scritto:
> this adds the proposed solution to add a generic mechanism to zeroize
> a target in qemu-img if it has discard_zeroes but has_zero_init is 0.
>
> Peter Lieven (4):
> block: add discard_zeroes and max_unmap to BlockDriverInfo
> iscsi: add .bdrv_ge
On Tue, Jul 16, 2013 at 12:48:36PM +0200, Paolo Bonzini wrote:
> Il 16/07/2013 12:37, Amos Kong ha scritto:
> > So here I defined a 'DataObject' type in qapi-schema.json,
> > it's used to describe the dynamical dictionary/list/string.
> >
> > { 'type': 'DataObject',
> > 'data': { '*key': 'str',
Il 16/07/2013 13:04, Amos Kong ha scritto:
>>> > > So here I defined a 'DataObject' type in qapi-schema.json,
>>> > > it's used to describe the dynamical dictionary/list/string.
>>> > >
>>> > > { 'type': 'DataObject',
>>> > > 'data': { '*key': 'str', '*type': 'str', '*data': ['DataObject'] } }
>
10.07.2013 02:03, Anthony Liguori wrote:
> Peter Maydell writes:
>
>> On 9 July 2013 22:24, Anthony Liguori wrote:
>>> Peter Maydell writes:
Why the heck are we telling the guest that the user
specified -nographic anyhow? It's a dumb guest ABI...
>>>
>>> I believe OpenBIOS uses this t
On 16.07.2013 12:55, Paolo Bonzini wrote:
Il 15/07/2013 12:49, Peter Lieven ha scritto:
this adds the proposed solution to add a generic mechanism to zeroize
a target in qemu-img if it has discard_zeroes but has_zero_init is 0.
Peter Lieven (4):
block: add discard_zeroes and max_unmap to Blo
Il 16/07/2013 13:18, Peter Lieven ha scritto:
>> Looks good. Perhaps, as a followup, you can use max_unmap (which I'd
>> rename to max_discard) in bdrv_co_discard to support splitting the
>> request. You could also export the discard alignment in BlockDriverInfo.
> I already did this in my previo
On Tue, Jul 16, 2013 at 10:25:29AM +0200, Kevin Wolf wrote:
> > - glusterfs_libs="-lgfapi -lgfrpc -lgfxdr"
> > - if compile_prog "" "$glusterfs_libs" ; then
> > -glusterfs=yes
> > -libs_tools="$glusterfs_libs $libs_tools"
> > -libs_softmmu="$glusterfs_libs $libs_softmmu"
> > + if $pk
Hello,
I want to implement an alternative mac address setting to allow a guest using
virtio-net to change it's mac address by itself.
The main use case is high availability setups where a slave machine take the
lead when the master is failing. (heartbeat)
The thing that an alternate mac address
On 10 July 2013 06:08, Michael Tokarev wrote:
> I updated the git branch on my site --
>
> http://git.corpit.ru/?p=qemu.git;a=shortlog;h=refs/heads/mjt-dt-nographic
>
> (two patches on the top). This now includes the `make check' fix by
> flipping the check (FW_CFG_NOGRAPHIC==1 vs ==0), more doc
On 16.07.2013 13:27, Paolo Bonzini wrote:
Il 16/07/2013 13:18, Peter Lieven ha scritto:
Looks good. Perhaps, as a followup, you can use max_unmap (which I'd
rename to max_discard) in bdrv_co_discard to support splitting the
request. You could also export the discard alignment in BlockDriverInf
On Sun, Jul 07, 2013 at 11:13:37PM +0800, Arthur Chunqi Li wrote:
> The recent KVM patch adds IA32_FEATURE_CONTROL support. QEMU needs
> to clear this MSR when reset vCPU and keep the value of it when
> migration. This patch add this feature.
>
So what happens if we migrate from qemu that does not
commit 9f328977 changes qmp_send_key() to accept key codes in hex,
but the document wasn't updated. The items of keys list is union
now, not enum.
Signed-off-by: Amos Kong
---
qmp-commands.hx | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/qmp-commands.hx b/qmp-command
Il 16/07/2013 13:40, Peter Lieven ha scritto:
>
> The conflict with your block status patches can't be large.
> upstream/master has no
> iscsi_co_is_allocated yet, so there should be no trouble.
Yes, whoever goes second has to change it to the new get_block_status
API. Kevin and Stefan can decid
On Tue, Jul 16, 2013 at 7:42 PM, Gleb Natapov wrote:
> On Sun, Jul 07, 2013 at 11:13:37PM +0800, Arthur Chunqi Li wrote:
>> The recent KVM patch adds IA32_FEATURE_CONTROL support. QEMU needs
>> to clear this MSR when reset vCPU and keep the value of it when
>> migration. This patch add this featur
Il 16/07/2013 13:42, Gleb Natapov ha scritto:
> On Sun, Jul 07, 2013 at 11:13:37PM +0800, Arthur Chunqi Li wrote:
>> The recent KVM patch adds IA32_FEATURE_CONTROL support. QEMU needs
>> to clear this MSR when reset vCPU and keep the value of it when
>> migration. This patch add this feature.
>>
>
On Tue, Jul 16, 2013 at 07:56:25PM +0800, Arthur Chunqi Li wrote:
> On Tue, Jul 16, 2013 at 7:42 PM, Gleb Natapov wrote:
> > On Sun, Jul 07, 2013 at 11:13:37PM +0800, Arthur Chunqi Li wrote:
> >> The recent KVM patch adds IA32_FEATURE_CONTROL support. QEMU needs
> >> to clear this MSR when reset v
On Tue, Jul 16, 2013 at 01:08:55PM +0200, Paolo Bonzini wrote:
> Il 16/07/2013 13:04, Amos Kong ha scritto:
> >>> > > So here I defined a 'DataObject' type in qapi-schema.json,
> >>> > > it's used to describe the dynamical dictionary/list/string.
> >>> > >
> >>> > > { 'type': 'DataObject',
> >>> >
On Tue, 16 Jul 2013 12:31:46 +0200
Paolo Bonzini wrote:
> Il 16/07/2013 12:19, Igor Mammedov ha scritto:
> > On Tue, 16 Jul 2013 08:19:48 +0200
> > Paolo Bonzini wrote:
> >
> >> Il 16/07/2013 03:27, Hu Tao ha scritto:
> I think it's the same. One "-numa mem" option = one "-device dimm"
>
Il 16/07/2013 14:00, Igor Mammedov ha scritto:
>>> we can leave -numa for initial memory mapping and manage of the mapping
>>> of hotpluggable regions with -device dimm,node=X,size=Y.
>>>
>>> It that case command line -device dimm will provide a fully initialized
>>> dimm device usable at startup (
Il 16/07/2013 14:04, Amos Kong ha scritto:
>> > Thanks. I see this is unique, but it is also not too intuitive.
>> >
>> > So, could you add a "kind" field to DataObject that is an enum
>> > (list/dict/scalar, or something like that)? This would make it easier
>> > to parse (for humans at least,
Am 15.07.2013 17:37, schrieb Paolo Bonzini:
> Il 15/07/2013 17:06, Andreas Färber ha scritto:
>> Am 15.07.2013 16:43, schrieb Paolo Bonzini:
>>> Il 15/07/2013 15:40, Andreas Färber ha scritto:
Originally Paolo and me had implemented QOM realize at Object level.
Paolo's goal was to set rea
We already have a qemu_devtree_setprop_cells() which sets a dtb
property to an array of cells whose values are specified by varargs.
However for the fairly common case of setting a property to a list
of addresses or of address,size pairs the number of cells used by
each element in the list depends
On 2013-05-30 23:03, Paolo Bonzini wrote:
> This provides the basics for detecting accesses to unassigned memory
> as soon as they happen, and also for a simple implementation of
> address_space_access_valid.
>
> Reviewed-by: Richard Henderson
> Signed-off-by: Paolo Bonzini
> ---
> exec.c |
Am 15.07.2013 11:34, schrieb Kevin Wolf:
> AHCI couldn't cope with asynchronous commands that aren't doing DMA, it
> simply wouldn't complete them. Due to the bug fixed in commit f68ec837,
> FLUSH commands would seem to have completed immediately even if they
> were still running on the host. After
Alexey Kardashevskiy writes:
> Signed-off-by: Alexey Kardashevskiy
> ---
> target-ppc/kvm.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/target-ppc/kvm.c b/target-ppc/kvm.c
> index 61f2737..606bdb9 100644
> --- a/target-ppc/kvm.c
> +++ b/target-ppc/kvm.c
> @@ -16
Alexey Kardashevskiy writes:
> On 07/16/2013 01:11 AM, Anthony Liguori wrote:
>> This series is based on Alexey's series:
>>
>> spapr: migration, pci, msi, power8
>>
>> Which in turn was based on work by David Gibson.
>>
>> I've removed the bits not related to migration and made the
>> follo
Il 16/07/2013 14:28, Jan Kiszka ha scritto:
> On 2013-05-30 23:03, Paolo Bonzini wrote:
>> This provides the basics for detecting accesses to unassigned memory
>> as soon as they happen, and also for a simple implementation of
>> address_space_access_valid.
>>
>> Reviewed-by: Richard Henderson
>>
Cornelia Huck writes:
> On Tue, 16 Jul 2013 15:10:41 +0800
> Stefan Hajnoczi wrote:
>
>> > Considering what the patch looks like, I don't think it's a huge
>> > problem... In fact, perhaps x-data-plane could be even added to
>> > DEFINE_VIRTIO_BLK_PROPERTIES. This would make it clear that supp
On 07/16/2013 10:33 PM, Anthony Liguori wrote:
> Alexey Kardashevskiy writes:
>
>> On 07/16/2013 01:11 AM, Anthony Liguori wrote:
>>> This series is based on Alexey's series:
>>>
>>> spapr: migration, pci, msi, power8
>>>
>>> Which in turn was based on work by David Gibson.
>>>
>>> I've removed
On Mon, Jul 15, 2013 at 11:34:31AM +0200, Kevin Wolf wrote:
> AHCI couldn't cope with asynchronous commands that aren't doing DMA, it
> simply wouldn't complete them. Due to the bug fixed in commit f68ec837,
> FLUSH commands would seem to have completed immediately even if they
> were still running
On 16 July 2013 13:33, Paolo Bonzini wrote:
> Il 16/07/2013 14:28, Jan Kiszka ha scritto:
>> This changed the value read from unassigned memory from -1 to 0. Any
>> particular reason or an unintentional change?
>
> Cut-and-paste (unassigned RAM used to return 0, invalid MMIO used to
> return -1, u
This restore the behavior prior to b018ddf633 which accidentally changed
the return code to 0. Specifically guests probing for register existence
were affected by this.
Signed-off-by: Jan Kiszka
---
memory.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/memory.c b/mem
Am 16.07.2013 um 14:30 hat Andreas Färber geschrieben:
> Am 15.07.2013 11:34, schrieb Kevin Wolf:
> > AHCI couldn't cope with asynchronous commands that aren't doing DMA, it
> > simply wouldn't complete them. Due to the bug fixed in commit f68ec837,
> > FLUSH commands would seem to have completed i
Il 16/07/2013 14:45, Jan Kiszka ha scritto:
> This restore the behavior prior to b018ddf633 which accidentally changed
> the return code to 0. Specifically guests probing for register existence
> were affected by this.
>
> Signed-off-by: Jan Kiszka
> ---
> memory.c |2 +-
> 1 files changed,
On 07/16/2013 10:35 PM, Alexey Kardashevskiy wrote:
> On 07/16/2013 10:33 PM, Anthony Liguori wrote:
>> Alexey Kardashevskiy writes:
>>
>>> On 07/16/2013 01:11 AM, Anthony Liguori wrote:
This series is based on Alexey's series:
spapr: migration, pci, msi, power8
Which in
Sorry for the gibberish I misread the code.
Please ignore this mail.
Best regards
Benoît
>Le Tuesday 16 Jul 2013 à 13:36:49 (+0200), Benoît Canet a écrit :
>
> Hello,
>
> I want to implement an alternative mac address setting to allow a guest using
> virtio-net to change it's mac address by i
On 2013-07-16 14:38, Peter Maydell wrote:
> On 16 July 2013 13:33, Paolo Bonzini wrote:
>> Il 16/07/2013 14:28, Jan Kiszka ha scritto:
>>> This changed the value read from unassigned memory from -1 to 0. Any
>>> particular reason or an unintentional change?
>>
>> Cut-and-paste (unassigned RAM used
Add some virtio-mmio transports to the vexpress board model,
together with a modify_dtb hook which adds them to the device
tree so that the kernel will probe for them. We put them
in a reserved area of the address map.
Signed-off-by: Peter Maydell
---
hw/arm/vexpress.c | 99 +++
Replace the opencoded assembly of the reg property array for the
/memory node with a call to qemu_devtree_setprop_sized_cells().
Signed-off-by: Peter Maydell
---
hw/arm/boot.c | 29 -
1 file changed, 8 insertions(+), 21 deletions(-)
diff --git a/hw/arm/boot.c b/hw/
Make the VEDBoardInfo struct extend arm_boot_info; this will
allow us to get at the VEDBoardInfo information inside callbacks
from arm/boot code.
Signed-off-by: Peter Maydell
---
hw/arm/vexpress.c | 31 +++
1 file changed, 15 insertions(+), 16 deletions(-)
diff --g
The MMIO virtio transport spec allows the guest to tell the host how
large the queue size is. Add virtio_queue_set_num() function which
implements this in the QEMU common virtio support code.
Signed-off-by: Peter Maydell
---
hw/virtio/virtio.c |8
include/hw/virtio/virtio.h
Support virtio transports which can specify the vring alignment
(ie where the guest communicates this to the host) by providing
a new virtio_queue_set_align() function. (The default alignment
remains as before.)
Transports which wish to make use of this must set the
has_variable_vring_alignment fi
This patch series adds an implementation of the virtio-mmio
transport, and uses it in the vexpress-a9 and vexpress-a15
board models.
The basic idea is that the board instantiates some transports,
the user can create backends which automatically plug into them
(via -device virtio-blk-backend and th
Add a callback hook in arm_boot_info to allow board models to
modify the device tree blob if they need to. (The major expected
use case is to add virtio-mmio nodes for virtio-mmio transports
that exist in QEMU but not in the hardware.)
Signed-off-by: Peter Maydell
---
hw/arm/boot.c|5
Add support for the generic MMIO based virtio transport.
This patch includes some fixes for bugs spotted by
Ying-Shiuan Pan .
Signed-off-by: Peter Maydell
[Fred changes: updated to new virtio-bus mechanisms]
Signed-off-by: KONRAD Frederic
[PMM changes:
* fixed trivial makefile conflict
* remo
On 07/16/2013 10:48 PM, Alexey Kardashevskiy wrote:
> On 07/16/2013 10:35 PM, Alexey Kardashevskiy wrote:
>> On 07/16/2013 10:33 PM, Anthony Liguori wrote:
>>> Alexey Kardashevskiy writes:
>>>
On 07/16/2013 01:11 AM, Anthony Liguori wrote:
> This series is based on Alexey's series:
>
Hi Peter,
On Tue, Jul 16, 2013 at 10:25 PM, Peter Maydell
wrote:
> We already have a qemu_devtree_setprop_cells() which sets a dtb
> property to an array of cells whose values are specified by varargs.
> However for the fairly common case of setting a property to a list
> of addresses or of addre
On 07/16/2013 05:52 AM, Amos Kong wrote:
> commit 9f328977 changes qmp_send_key() to accept key codes in hex,
> but the document wasn't updated. The items of keys list is union
> now, not enum.
>
> Signed-off-by: Amos Kong
> ---
> qmp-commands.hx | 7 +--
> 1 file changed, 5 insertions(+), 2
On Tue, 16 Jul 2013 09:27:27 +0800
Saptarshi Sen wrote:
> Hi,
>
>Is it possible to use fixed array data structures for use through the
> qmp-interface.
>
>My aim is to monitor IDE level activity in terms of sectors being
> accessed. So
>I plan to have a fixed size buffer. But I find
Am 01.07.2013 12:18, schrieb Hu Tao:
> Introduce type constant and avoid FROM_SYSBUS().
>
> Signed-off-by: Hu Tao
> ---
> hw/i386/kvm/clock.c | 9 ++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
Thanks, by now I've picked up all remaining QOM cast patches (and
renamed and marked up
Quoting Saptarshi Sen (2013-07-15 20:27:27)
> Hi,
>
> Is it possible to use fixed array data structures for use through the
>qmp-interface.
>
> My aim is to monitor IDE level activity in terms of sectors being
>accessed. So
> I plan to have a fixed size buffer. But I
Alexey Kardashevskiy writes:
> On 07/16/2013 10:48 PM, Alexey Kardashevskiy wrote:
>> On 07/16/2013 10:35 PM, Alexey Kardashevskiy wrote:
>>> On 07/16/2013 10:33 PM, Anthony Liguori wrote:
Alexey Kardashevskiy writes:
> On 07/16/2013 01:11 AM, Anthony Liguori wrote:
>> This ser
Am 16.07.2013 04:00, schrieb Jia Liu:
> We should free typename here.
>
> Signed-off-by: Jia Liu
> ---
> target-openrisc/cpu.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/target-openrisc/cpu.c b/target-openrisc/cpu.c
> index 6d40f1b..e348df0 100644
> --- a/target-openrisc/cpu.c
> +
Hi Peter,
On Tue, Jul 16, 2013 at 10:25 PM, Peter Maydell
wrote:
> Replace the opencoded assembly of the reg property array for the
> /memory node with a call to qemu_devtree_setprop_sized_cells().
>
> Signed-off-by: Peter Maydell
> ---
> hw/arm/boot.c | 29 -
> 1
On 16 July 2013 15:31, Peter Crosthwaite wrote:
> Hi Peter,
>
> On Tue, Jul 16, 2013 at 10:25 PM, Peter Maydell
> wrote:
>> Replace the opencoded assembly of the reg property array for the
>> /memory node with a call to qemu_devtree_setprop_sized_cells().
>>
>> Signed-off-by: Peter Maydell
>> --
For usb-ehci in qemu, its caps just has read() operation,
the write() operation does not exist.
This cause a Segmentation fault when use usb-ehci device in ppc64
platform.
here is gdb output:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x3fffa7fcef20 (LWP 6793)]
0x0
On Tue, 16 Jul 2013 11:05:11 +0800
Stefan Hajnoczi wrote:
> On Mon, Jul 15, 2013 at 09:41:19PM +0200, Christian Borntraeger wrote:
> > When running with trace backend e.g. "simple" the writer thread
> > needs to be implemented in the same process context as the trace
> > points that will be proce
On 07/16/2013 04:06 AM, Scott Wood wrote:
> On 07/10/2013 12:10:02 PM, Fabien Chouteau wrote:
>> This implementation doesn't include ring priority, TCP/IP Off-Load, QoS.
>>
>> Signed-off-by: Fabien Chouteau
>
> From the code comments I gather this has been tested on VxWorks. Has it
> been tested
Paolo,
--On 16 July 2013 09:34:20 +0200 Paolo Bonzini wrote:
You did. But aio_wait() ignores the timeout. It is only used by the
main loop.
OK well that seems worth fixing in any case, as even without timed bh's
that means no bh can be executed for an indeterminate time. I'll have
a look a
From: Peter Maydell
Commit e3127ae0 introduced a problem where we're passing a
hwaddr* to qemu_ram_ptr_length() but it wants a ram_addr_t*;
this will cause problems on 32 bit hosts and in any case
provokes a clang warning on MacOSX:
CCarm-softmmu/exec.o
exec.c:2164:46: warning: incompatibl
Three fixes from Peter, Jan and me. I'm still recovering from the email
backlog, hence I don't trust myself sending a pull request... In any
case, they are available also from
git://github.com/bonzini/qemu.git iommu-from-anthony
Paolo
Jan Kiszka (1):
memory: Return -1 again on reads from u
Brown paper bag for me. Commit 2c9b15c added a line setting mr->owner,
but there was already one that initialized it to NULL (added in the
earlier commit 803c0816).
Signed-off-by: Paolo Bonzini
---
memory.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/memory.c b/memory.c
index c8f9a2b..99
From: Jan Kiszka
This restore the behavior prior to b018ddf633 which accidentally changed
the return code to 0. Specifically guests probing for register existence
were affected by this.
Signed-off-by: Jan Kiszka
Signed-off-by: Paolo Bonzini
---
memory.c | 2 +-
1 file changed, 1 insertion(+),
On 07/16/2013 05:28 PM, Fabien Chouteau wrote:
On 07/16/2013 04:06 AM, Scott Wood wrote:
On 07/10/2013 12:10:02 PM, Fabien Chouteau wrote:
This implementation doesn't include ring priority, TCP/IP Off-Load, QoS.
Signed-off-by: Fabien Chouteau
From the code comments I gather this has been tes
Il 16/07/2013 17:29, Alex Bligh ha scritto:
> Paolo,
>
> --On 16 July 2013 09:34:20 +0200 Paolo Bonzini wrote:
>
You did. But aio_wait() ignores the timeout. It is only used by the
main loop.
>>>
>>> OK well that seems worth fixing in any case, as even without timed bh's
>>> that mea
Paolo,
3. aio_poll calls aio_bh_poll. If this returns true, this indicates
at least one non-idle bh exists, which causes aio_poll not to
block.
No, this indicates that at least one scheduled non-idle bh exist*ed*,
which causes aio_poll not to block (because some progress has been done).
1 - 100 of 206 matches
Mail list logo
