On Thu, May 24, 2018 at 10:24:40AM +0800, Tiwei Bie wrote:
[...]
> > > +
> > > qemu_purge_queued_packets(nc);
> > > }
> > >
> > > @@ -341,7 +342,6 @@ err:
> > > if (user) {
> > > vhost_user_cleanup(user);
> > > g_free(user);
> > > -s->vhost_user = NULL;
>
> I
On Wed, May 23, 2018 at 11:14:11AM +0200, Juan Quintela wrote:
> Commit:
>
> commit 36c2f8be2c4eb0003ac77a14910842b7ddd7337e
> Author: Juan Quintela
> Date: Wed Mar 7 08:40:52 2018 +0100
>
> migration: Delay start of migration main routines
>
> Missed tcp and fd transports. This fix its.
Peter Xu writes:
> On Mon, May 21, 2018 at 09:13:06AM -0500, Eric Blake wrote:
>> On 05/21/2018 03:42 AM, Peter Xu wrote:
>> > We turned Out-Of-Band feature of monitors off for 2.12 release. Now we
>> > try to turn that on again.
>>
>> "try to turn" sounds weak, like you aren't sure of this pat
On Wed, 23 May 2018 19:28:31 +0200
Halil Pasic wrote:
> On 05/23/2018 06:59 PM, Cornelia Huck wrote:
> > On Wed, 23 May 2018 18:23:44 +0200
> > Halil Pasic wrote:
> >
> >> On 05/23/2018 04:46 PM, Cornelia Huck wrote:
> >> +if (!(sch->orb.ctrl0 & ORB_CTRL0_MASK_PFCH)) {
> >> +
> On Tue, May 22, 2018 at 10:08 PM, Yasunori Goto wrote:
> > Hello,
> >
> > I'm investigating status of vNVDIMM on qemu/KVM,
> > and I have some questions about it. I'm glad if anyone answer them.
> >
> > In my understanding, qemu/KVM has a feature to show NFIT for guest,
> > and it will be still
On Thu, May 24, 2018 at 09:08:58AM +0200, Markus Armbruster wrote:
> Peter Xu writes:
>
> > On Mon, May 21, 2018 at 09:13:06AM -0500, Eric Blake wrote:
> >> On 05/21/2018 03:42 AM, Peter Xu wrote:
> >> > We turned Out-Of-Band feature of monitors off for 2.12 release. Now we
> >> > try to turn th
On Mon, 05/21 16:58, Fam Zheng wrote:
> Coverity doesn't like the tests under fail label (report CID 1385847).
> Reset the fields so the clean up order is more apparent.
>
> Signed-off-by: Fam Zheng
Queued, thanks.
Fam
On 05/23/2018 02:17 PM, Yi Min Zhao wrote:
在 2018/5/23 下午6:33, Eduardo Otubo 写道:
On 05/23/2018 11:16 AM, Yi Min Zhao wrote:
在 2018/5/23 下午3:47, Ján Tomko 写道:
On Sat, May 19, 2018 at 04:20:37PM +0800, Yi Min Zhao wrote:
在 2018/5/18 下午9:07, Ján Tomko 写道:
On Fri, May 18, 2018 at 11:19:16A
On Thu, May 24, 2018 at 08:04:59AM +0200, Paolo Bonzini wrote:
> On 23/05/2018 16:46, Greg Kurz wrote:
> > Maybe change bdrv_root_unref_child() to ensure we don't call
> > bdrv_close() with pending I/O requests ?
> >
> > void bdrv_root_unref_child(BdrvChild *child)
> > {
> > BlockDriverStat
On Thu, May 24, 2018 at 12:39:51PM +0800, Peter Xu wrote:
> Add some explicit comment for both Readline and cpu_set/cpu_get helpers
> that they do not need the mon_lock protection.
>
> Signed-off-by: Peter Xu
> ---
> monitor.c | 12 +++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
On 24/05/18 06:39, Mark Cave-Ayland wrote:
Commit 72d3d8f052 "hw/isa/superio: Add a keyboard/mouse controller (8042)"
added an 8042 keyboard device to the PC87312 superio device to replace that
being used by the prep machine.
Unfortunately this commit didn't do the same for the 40p machine whic
Am 24.05.2018 um 00:24 hat John Snow geschrieben:
>
>
> On 05/18/2018 09:20 AM, Kevin Wolf wrote:
> > +job->auto_finalize = !(flags & JOB_MANUAL_FINALIZE);
> > +job->auto_dismiss = !(flags & JOB_MANUAL_DISMISS);
>
> Job API might be a good chance to say "No, this is the default behavior
Peter Xu writes:
> On Wed, May 23, 2018 at 03:13:07PM +0200, Markus Armbruster wrote:
>> Peter Xu writes:
>>
>> > On Wed, May 23, 2018 at 10:23:22AM +0200, Markus Armbruster wrote:
>> >> Peter Xu writes:
>> >>
>> >> > In the future the monitor iothread may be accessing the cur_mon as
>> >> >
Am 24.05.2018 um 01:18 hat John Snow geschrieben:
> > diff --git a/include/qemu/job.h b/include/qemu/job.h
> > index 3e817beee9..2648c74281 100644
> > --- a/include/qemu/job.h
> > +++ b/include/qemu/job.h
> > @@ -97,6 +97,12 @@ typedef struct Job {
> > */
> > bool cancelled;
> >
> > +
On Wed, 05/23 13:28, Eric Blake wrote:
> On 05/22/2018 10:04 PM, Fam Zheng wrote:
> > We don't verify the request range against s->size in the I/O callbacks
> > except for raw_co_pwritev. This is wrong (especially for
> > raw_co_pwrite_zeroes and raw_co_pdiscard), so fix them.
>
> I'd also mention
Peter Xu writes:
> The out_lock is protecting a few Monitor fields. In the future the
> monitor code will start to run in multiple threads. We are going to
> turn it into a bigger lock to protect not only the out buffer but also
> all the rest.
Hmm, not sure about "all the rest": PATCH 3 marks
Am 24.05.2018 um 01:42 hat John Snow geschrieben:
> On 05/18/2018 09:21 AM, Kevin Wolf wrote:
> > Instead of having a 'bool ready' in BlockJob, add a function that
> > derives its value from the job status.
> >
> > At the same time, this fixes the behaviour to match what the QAPI
> > documentation
On Thu, 24 May 2018 09:05:53 +0100
Stefan Hajnoczi wrote:
> On Thu, May 24, 2018 at 08:04:59AM +0200, Paolo Bonzini wrote:
> > On 23/05/2018 16:46, Greg Kurz wrote:
> > > Maybe change bdrv_root_unref_child() to ensure we don't call
> > > bdrv_close() with pending I/O requests ?
> > >
> > > vo
Am 24.05.2018 um 02:02 hat John Snow geschrieben:
>
>
> On 05/18/2018 09:21 AM, Kevin Wolf wrote:
> > This adds a QMP event that is emitted whenever a job transitions from
> > one status to another.
> >
> > Signed-off-by: Kevin Wolf
>
> That's a lot of events, and a lot are redundant to what w
Regarding the subject: what are "fleids"?
Peter Xu writes:
> Add some explicit comment for both Readline and cpu_set/cpu_get helpers
> that they do not need the mon_lock protection.
>
> Signed-off-by: Peter Xu
> ---
> monitor.c | 12 +++-
> 1 file changed, 11 insertions(+), 1 deletion(
On Thu, May 24, 2018 at 10:22:48AM +0200, Markus Armbruster wrote:
> Peter Xu writes:
>
> > On Wed, May 23, 2018 at 03:13:07PM +0200, Markus Armbruster wrote:
> >> Peter Xu writes:
> >>
> >> > On Wed, May 23, 2018 at 10:23:22AM +0200, Markus Armbruster wrote:
> >> >> Peter Xu writes:
> >> >>
On Thu, May 24, 2018 at 10:29:20AM +0200, Markus Armbruster wrote:
> Peter Xu writes:
>
> > The out_lock is protecting a few Monitor fields. In the future the
> > monitor code will start to run in multiple threads. We are going to
> > turn it into a bigger lock to protect not only the out buffe
On Thu, May 24, 2018 at 09:08:04AM +0100, Stefan Hajnoczi wrote:
> On Thu, May 24, 2018 at 12:39:51PM +0800, Peter Xu wrote:
> > Add some explicit comment for both Readline and cpu_set/cpu_get helpers
> > that they do not need the mon_lock protection.
> >
> > Signed-off-by: Peter Xu
> > ---
> >
On Thu, May 24, 2018 at 10:41:09AM +0200, Markus Armbruster wrote:
> Regarding the subject: what are "fleids"?
Ouch. :( I meant the word "fields".
>
> Peter Xu writes:
>
> > Add some explicit comment for both Readline and cpu_set/cpu_get helpers
> > that they do not need the mon_lock protectio
Peter Xu writes:
> Similar to previous patch, but introduce a new global big lock for
> mon_fdsets. Take it where needed.
The previous patch is "monitor: more comments on lock-free
fleids/funcs". Sure you mean that one?
>
> The monitor_fdset_get_fd() handling is a bit tricky: now we need to ca
Hi Shannon,
On 05/23/2018 05:53 AM, Shannon Zhao wrote:
> While we skip the GIC_INTERNAL irqs, we don't change the register offset
> accordingly. This will overlap the GICR registers value and leave the
> last GIC_INTERNAL irq's registers out of update.
>
> Fix this by skipping the registers bank
Removing a drive with drive_del while it is being used to run an I/O
intensive workload can cause QEMU to crash.
An AIO flush can yield at some point:
blk_aio_flush_entry()
blk_co_flush(blk)
bdrv_co_flush(blk->root->bs)
...
qemu_coroutine_yield()
and let the HMP command to run, free bl
On 23 May 2018 at 21:52, Laszlo Ersek wrote:
> On 05/23/18 22:40, Auger Eric wrote:
>> On 05/23/2018 07:45 PM, Laszlo Ersek wrote:
>
>>> Regarding the second patch, I do believe we need "more sophistication"
>>> there. For example, I guess it could be possible to distinguish "-cpu
>>> cortex-a15"
On 2018/5/24 17:04, Auger Eric wrote:
> Hi Shannon,
>
> On 05/23/2018 05:53 AM, Shannon Zhao wrote:
>> While we skip the GIC_INTERNAL irqs, we don't change the register offset
>> accordingly. This will overlap the GICR registers value and leave the
>> last GIC_INTERNAL irq's registers out of upd
On Thu, May 24, 2018 at 12:39:52PM +0800, Peter Xu wrote:
> int monitor_fdset_get_fd(int64_t fdset_id, int flags)
> {
> -#ifndef _WIN32
> +#ifdef _WIN32
> +return -ENOENT;
stubs/fdset.c:monitor_fdset_get_fd() should return -ENOENT instead of -1
now.
signature.asc
Description: PGP signature
> > The original purpose was just to support multiple segments in Intel
> > Q35 archtecure for PCIe topology, which makes bus number a less scarce
> > resource. The patches are very primitive and many things are left for
> > firmware to finish(the initial plan was to implement it in SeaBIOS),
> > t
On Mon, May 21, 2018 at 05:33:22PM -0300, Eduardo Habkost wrote:
> On Mon, May 21, 2018 at 09:18:17PM +0100, Daniel P. Berrangé wrote:
[...]
(Just catching up with this thread.)
[...]
> > > I have very specific goal here: the goal is to make it less
> > > painful to users when OpenStack+libvirt
2018-05-24 1:33 GMT+08:00 Marcel Apfelbaum :
>
>> * IOMMUs cannot span domains either, so bringing new domains introduces
>> the need
>> to add a VT-d DHRD or vIOMMU per PCIe domain
>
>
> Not really, you may have PCI domains not associated to an vIOMMU. As a first
> step,
> you should not deal wi
On 22 May 2018 at 19:33, Michael Walle wrote:
> Am 2018-05-22 12:01, schrieb Peter Maydell:
>>
>> On 21 May 2018 at 16:49, Michael Walle wrote:
>>>
>>> The following changes since commit
>>> 81e9cbd0ca1131012b058df6804b1f626a6b730c:
>>>
>>> lm32: take BQL before writing IP/IM register (2018-05-
On 05/24/2018 09:16 AM, Cornelia Huck wrote:
On Wed, 23 May 2018 19:28:31 +0200
Halil Pasic wrote:
On 05/23/2018 06:59 PM, Cornelia Huck wrote:
On Wed, 23 May 2018 18:23:44 +0200
Halil Pasic wrote:
On 05/23/2018 04:46 PM, Cornelia Huck wrote:
+if (!(sch->orb.ctrl0 & ORB_CTRL0_MAS
This patch set depends on below patch set:
http://lists.gnu.org/archive/html/qemu-devel/2018-05/msg05335.html
More details about this patch set can be found from:
http://lists.gnu.org/archive/html/qemu-devel/2018-04/msg01779.html
http://lists.gnu.org/archive/html/qemu-devel/2018-04/msg04626.html
This patch introduces VHOST_USER_PROTOCOL_F_HOST_NOTIFIER.
With this feature negotiated, vhost-user backend can register
memory region based host notifiers. And it will allow the guest
driver in the VM to notify the hardware accelerator at the
vhost-user backend directly.
Signed-off-by: Tiwei Bie
When multi queue is enabled e.g. for a virtio-net device,
each queue pair will have a vhost_dev, and the only thing
shared between vhost devs currently is the chardev. This
patch introduces a vhost-user state structure which will
be shared by all vhost devs of the same virtio device.
Signed-off-by
On Thu, 24 May 2018 12:29:01 +0200
Halil Pasic wrote:
> On 05/24/2018 09:16 AM, Cornelia Huck wrote:
> > On Wed, 23 May 2018 19:28:31 +0200
> > Halil Pasic wrote:
> >
> >> On 05/23/2018 06:59 PM, Cornelia Huck wrote:
> >>> On Wed, 23 May 2018 18:23:44 +0200
> >>> Halil Pasic wrote:
> >>>
This patch introduces a vhost op for vhost backends to allow
them to filter the memory sections that they can handle.
Signed-off-by: Tiwei Bie
---
hw/virtio/vhost-user.c| 11 +++
hw/virtio/vhost.c | 9 +++--
include/hw/virtio/vhost-backend.h | 4
3
Introduce VHOST_USER_PROTOCOL_F_SLAVE_SEND_FD protocol
feature to allow slave to send at most 8 descriptors
in each message to master via ancillary data using the
slave channel.
Suggested-by: Michael S. Tsirkin
Signed-off-by: Tiwei Bie
---
docs/interop/vhost-user.txt | 5 +
hw/virtio/vhost
This patch introduces the host notifier support in
libvhost-user. A new API is added to support setting
host notifier for each queue.
Signed-off-by: Tiwei Bie
---
contrib/libvhost-user/libvhost-user.c | 81 ---
contrib/libvhost-user/libvhost-user.h | 32 +++
2 fil
This patch introduces the host notifier support in
vhost-user-bridge. A new option (-H) is added to use
the host notifier. This is mainly used to test the
host notifier implementation in vhost user.
Signed-off-by: Tiwei Bie
---
tests/vhost-user-bridge.c | 98 +
On 24 May 2018 at 07:23, Peter Xu wrote:
> On Wed, May 23, 2018 at 12:47:16PM +0100, Peter Maydell wrote:
>> On 23 May 2018 at 02:06, Peter Xu wrote:
>> > Could you elaborate a bit more on why IOMMU notifier failed to
>> > corporate when passing in MemTxAttrs? I am not sure I caught the idea
>>
On Thu, May 24, 2018 at 10:24:40AM +0800, Tiwei Bie wrote:
> On Thu, May 24, 2018 at 07:21:01AM +0800, Tiwei Bie wrote:
> > On Wed, May 23, 2018 at 06:43:29PM +0300, Michael S. Tsirkin wrote:
> > > On Wed, May 23, 2018 at 06:36:05PM +0300, Michael S. Tsirkin wrote:
> > > > On Wed, May 23, 2018 at 0
Peter Xu writes:
> On Thu, May 24, 2018 at 10:29:20AM +0200, Markus Armbruster wrote:
>> Peter Xu writes:
>>
>> > The out_lock is protecting a few Monitor fields. In the future the
>> > monitor code will start to run in multiple threads. We are going to
>> > turn it into a bigger lock to prot
Peter Xu writes:
> On Thu, May 24, 2018 at 10:22:48AM +0200, Markus Armbruster wrote:
>> Peter Xu writes:
>>
>> > On Wed, May 23, 2018 at 03:13:07PM +0200, Markus Armbruster wrote:
>> >> Peter Xu writes:
>> >>
>> >> > On Wed, May 23, 2018 at 10:23:22AM +0200, Markus Armbruster wrote:
>> >> >>
On Fri, May 18, 2018 at 06:09:56PM +0100, Daniel P. Berrangé wrote:
> The closest to a cross-hypervisor standard is OVF which can store
> metadata about required hardware for a VM. I'm pretty sure it does
> not have the concept of machine types, but maybe it has a way for
> people to define metadat
Peter Xu writes:
> On Thu, May 24, 2018 at 10:41:09AM +0200, Markus Armbruster wrote:
>> Regarding the subject: what are "fleids"?
>
> Ouch. :( I meant the word "fields".
Can touch that up in my tree.
>> Peter Xu writes:
>>
>> > Add some explicit comment for both Readline and cpu_set/cpu_get
This patch adds Intel Hexadecimal Object File format support to
the loader. The file format specification is available here:
http://www.piclist.com/techref/fileext/hex/intel.htm
The file format is mainly intended for embedded systems
and microcontrollers, such as Micro:bit Arduino, ARM, STM32, et
'test.hex' file is a bare metal ARM software stored in Hexadecimal
Object Format. When it's loaded by QEMU, it will print "Hello world!\n"
on console.
`pre_store` array in 'hexloader-test.c' file, stores the binary format
of 'test.hex' file, which is used to verify correctness.
Reviewed-by: Stefa
The following changes since commit 9cac60db4513f968b56e12720c1ea433be318cc3:
Merge remote-tracking branch 'remotes/mwalle/tags/lm32-queue/20180521' into
staging (2018-05-24 10:25:43 +0100)
are available in the git repository at:
git://github.com/DarcySail/qemu.git foo.for-upstream
for you
I read the whole thread and the fundamental problem is that you're
mixing layers. Let qcow2 be a disk image format, and let management
layers deal with metadata and how to run qemu.
What's going to happen when you have (eg) an OVA file containing qcow2
files, and the qcow2 files all have differen
Hi Aaron
On 05/24/2018 12:31 PM, Wei, Aaron wrote:
Hi, Marcel
It's my pleasure to write to you on behalf of a team who is developing
the Intel VMD virtualization base on QEMU in Dell EMC.
From https://www.outreachy.org. we find that you are working on the
Multiple PCI domain feature which
Hi Shannon,
On 05/24/2018 11:20 AM, Shannon Zhao wrote:
>
>
> On 2018/5/24 17:04, Auger Eric wrote:
>> Hi Shannon,
>>
>> On 05/23/2018 05:53 AM, Shannon Zhao wrote:
>>> While we skip the GIC_INTERNAL irqs, we don't change the register offset
>>> accordingly. This will overlap the GICR registers
On 22 May 2018 at 19:46, Stefano Stabellini wrote:
> The following changes since commit d32e41a1188e929cc0fb16829ce3736046951e39:
>
> Merge remote-tracking branch
> 'remotes/famz/tags/docker-and-block-pull-request' into staging (2018-05-18
> 14:11:52 +0100)
>
> are available in the git reposit
On 23 May 2018 at 06:10, Laurent Desnogues wrote:
> Some AArch64 tests I had that previously failed on a x86-64 host now pass.
>
> Tested-by: Laurent Desnogues
Thanks for the testing.
> Perhaps the two occurrences of the following comment in
> target/arm/translate-a64.c could be removed along w
Hi, Marcel
It's my pleasure to write to you on behalf of a team who is developing the
Intel VMD virtualization base on QEMU in Dell EMC.
>From https://www.outreachy.org. we find that you are working on the Multiple
>PCI domain feature which we think may be very helpful to our current work.
We
On 23 May 2018 at 04:53, Shannon Zhao wrote:
> It forgot to increase clroffset during the loop. So it only clear the
> first 4 bytes.
>
> Fixes: 367b9f527becdd20ddf116e17a3c0c2bbc486920
> Cc: qemu-sta...@nongnu.org
> Signed-off-by: Shannon Zhao
> Reviewed-by: Eric Auger
> ---
> Changes in V3: Ad
On 05/24/18 11:11, Peter Maydell wrote:
> On 23 May 2018 at 21:52, Laszlo Ersek wrote:
>> On 05/23/18 22:40, Auger Eric wrote:
>>> On 05/23/2018 07:45 PM, Laszlo Ersek wrote:
>>
Regarding the second patch, I do believe we need "more sophistication"
there. For example, I guess it could be
On Thu, May 24, 2018 at 2:28 PM, Peter Maydell wrote:
> On 23 May 2018 at 06:10, Laurent Desnogues
> wrote:
>> Some AArch64 tests I had that previously failed on a x86-64 host now pass.
>>
>> Tested-by: Laurent Desnogues
>
> Thanks for the testing.
>
>> Perhaps the two occurrences of the follow
On 24 May 2018 at 13:59, Laszlo Ersek wrote:
> On 05/24/18 11:11, Peter Maydell wrote:
>> Won't it also break a guest which is just Linux loaded not via
>> firmware which is an aarch32 kernel without LPAE support?
>
> Does such a thing exist? (I honestly have no clue.)
Yes, it does; LPAE isn't a
Hi Peter, Laszlo,
On 05/24/2018 03:07 PM, Peter Maydell wrote:
> On 24 May 2018 at 13:59, Laszlo Ersek wrote:
>> On 05/24/18 11:11, Peter Maydell wrote:
>>> Won't it also break a guest which is just Linux loaded not via
>>> firmware which is an aarch32 kernel without LPAE support?
>>
>> Does such
On 23 May 2018 at 04:53, Shannon Zhao wrote:
> While we skip the GIC_INTERNAL irqs, we don't change the register offset
> accordingly. This will overlap the GICR registers value and leave the
> last GIC_INTERNAL irq's registers out of update.
>
> Fix this by skipping the registers banked by GICR.
On 24 May 2018 at 10:04, Auger Eric wrote:
> Now I am unclear about the semantics of the s->gicd_ipriority & friends.
> With that change, is it supposed to contain only the states of SPIs or
> contain the RAZ states of PPI/SGIs + states of SPIs. The array is
> dimensionned to contain states for PP
On 22 May 2018 at 18:56, Richard Henderson wrote:
> Depending on the host abi, float16, aka uint16_t, values are
> passed and returned either zero-extended in the host register
> or with garbage at the top of the host register.
>
> The tcg code generator has so far been assuming garbage, as that
>
On 23 May 2018 at 14:11, Kevin Wolf wrote:
> The following changes since commit 4f50c1673a89b07f376ce5c42d22d79a79cd466d:
>
> Merge remote-tracking branch 'remotes/ehabkost/tags/x86-next-pull-request'
> into staging (2018-05-22 09:43:58 +0100)
>
> are available in the git repository at:
>
> g
On Mon 05 Jun 2017 02:39:08 PM CEST, Paolo Bonzini wrote:
> @@ -102,6 +107,8 @@ static void block_account_one_io(BlockAcctStats *stats,
> BlockAcctCookie *cookie,
>
> assert(cookie->type < BLOCK_MAX_IOTYPE);
>
> +qemu_mutex_lock(&stats->lock);
QEMU crashes because this lock is not in
On 24/05/2018 09:53, Eduardo Otubo wrote:
>
Thanks! But I have not got response from Paolo. I have added him to
CC list.
>>> I'll just wait one more ACK and will send a pull request on the
>>> seccomp queue. Thanks for the contribution.
>>>
>>>
>> So... what I should do is wait
On 23 May 2018 at 11:45, Eva Chen wrote:
> Hi,
>
> I have added a new virtual device under qemu/hw, and a device driver in the
> source code of guest OS (I use arm linux).
> Since I want to add an interrupt to the virtual device, I am tracing the
> flow of interrupt simulation of QEMU.
> However,
On Thu, May 24, 2018 at 07:12:15AM +0800, Tiwei Bie wrote:
> On Thu, May 24, 2018 at 12:25:23AM +0300, Michael S. Tsirkin wrote:
> > On Thu, Apr 12, 2018 at 11:12:29PM +0800, Tiwei Bie wrote:
> > > Signed-off-by: Tiwei Bie
> >
> >
> > Thinking about it, I think we should add a protocol
> > featu
On Thu 24 May 2018 03:35:50 PM CEST, Alberto Garcia wrote:
> On Mon 05 Jun 2017 02:39:08 PM CEST, Paolo Bonzini wrote:
>> @@ -102,6 +107,8 @@ static void block_account_one_io(BlockAcctStats *stats,
>> BlockAcctCookie *cookie,
>>
>> assert(cookie->type < BLOCK_MAX_IOTYPE);
>>
>> +qemu_
On 24/05/2018 15:35, Alberto Garcia wrote:
> On Mon 05 Jun 2017 02:39:08 PM CEST, Paolo Bonzini wrote:
>> @@ -102,6 +107,8 @@ static void block_account_one_io(BlockAcctStats *stats,
>> BlockAcctCookie *cookie,
>>
>> assert(cookie->type < BLOCK_MAX_IOTYPE);
>>
>> +qemu_mutex_lock(&stat
On Thu, May 24, 2018 at 10:24:40AM +0800, Tiwei Bie wrote:
> On Thu, May 24, 2018 at 07:21:01AM +0800, Tiwei Bie wrote:
> > On Wed, May 23, 2018 at 06:43:29PM +0300, Michael S. Tsirkin wrote:
> > > On Wed, May 23, 2018 at 06:36:05PM +0300, Michael S. Tsirkin wrote:
> > > > On Wed, May 23, 2018 at 0
On Tue, May 15, 2018 at 04:35:48PM +0200, Paolo Bonzini wrote:
> The function has been deprecated for 2.5 years, and there are just a handful
> of users. Convert them to memory_region_init_io with NULL callbacks,
> and while at it pass the right device as the owner.
>
> Signed-off-by: Paolo Bonzi
On Thu, May 24, 2018 at 06:59:36PM +0800, Tiwei Bie wrote:
> On Thu, May 24, 2018 at 10:24:40AM +0800, Tiwei Bie wrote:
> > On Thu, May 24, 2018 at 07:21:01AM +0800, Tiwei Bie wrote:
> > > On Wed, May 23, 2018 at 06:43:29PM +0300, Michael S. Tsirkin wrote:
> > > > On Wed, May 23, 2018 at 06:36:05PM
Hi,
On 05/24/2018 03:14 PM, Peter Maydell wrote:
> On 24 May 2018 at 10:04, Auger Eric wrote:
>> Now I am unclear about the semantics of the s->gicd_ipriority & friends.
>> With that change, is it supposed to contain only the states of SPIs or
>> contain the RAZ states of PPI/SGIs + states of SPI
On 05/24/18 15:07, Peter Maydell wrote:
> On 24 May 2018 at 13:59, Laszlo Ersek wrote:
>> On 05/24/18 11:11, Peter Maydell wrote:
>>> Won't it also break a guest which is just Linux loaded not via
>>> firmware which is an aarch32 kernel without LPAE support?
>>
>> Does such a thing exist? (I hones
On Tue, May 15, 2018 at 06:25:46PM -0300, Daniel Henrique Barboza wrote:
> This means that the test executed a write at LBA 0x94fa and, after
> confirming that the write was completed, issue 2 reads in the same LBA to
> assert the written contents and found out a mismatch.
Have you confirmed this
On Thu, May 24, 2018 at 12:19 AM, Yasunori Goto wrote:
>> On Tue, May 22, 2018 at 10:08 PM, Yasunori Goto
>> wrote:
>> > Hello,
>> >
>> > I'm investigating status of vNVDIMM on qemu/KVM,
>> > and I have some questions about it. I'm glad if anyone answer them.
>> >
>> > In my understanding, qemu/
Hi Laszlo,
On 05/24/2018 03:59 PM, Laszlo Ersek wrote:
> On 05/24/18 15:07, Peter Maydell wrote:
>> On 24 May 2018 at 13:59, Laszlo Ersek wrote:
>>> On 05/24/18 11:11, Peter Maydell wrote:
Won't it also break a guest which is just Linux loaded not via
firmware which is an aarch32 kernel
On 24 May 2018 at 15:59, Laszlo Ersek wrote:
> On 05/24/18 15:07, Peter Maydell wrote:
>> On 24 May 2018 at 13:59, Laszlo Ersek wrote:
>>> On 05/24/18 11:11, Peter Maydell wrote:
Won't it also break a guest which is just Linux loaded not via
firmware which is an aarch32 kernel without L
David, looks like your turf.
Collin Walling writes:
> When a user incorrectly provides an hmp command, an error response will be
> printed that prompts the user to try "help ". However, when
> the command contains multiple parts e.g. "info uuid xyz", only the last
> whitespace delimited string w
On 24 May 2018 at 14:59, Auger Eric wrote:
> Hi,
>
> On 05/24/2018 03:14 PM, Peter Maydell wrote:
>> On 24 May 2018 at 10:04, Auger Eric wrote:
>>> Now I am unclear about the semantics of the s->gicd_ipriority & friends.
>>> With that change, is it supposed to contain only the states of SPIs or
>
On 23 May 2018 at 15:42, Michael S. Tsirkin wrote:
> The following changes since commit 4f50c1673a89b07f376ce5c42d22d79a79cd466d:
>
> Merge remote-tracking branch 'remotes/ehabkost/tags/x86-next-pull-request'
> into staging (2018-05-22 09:43:58 +0100)
>
> are available in the git repository at:
Right now tests report OK status if QEMU crashes during cleanup.
Let's catch that case and fail the test.
Signed-off-by: Michael S. Tsirkin
---
tests/libqtest.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/tests/libqtest.c b/tests/libqtest.c
index 43fb97e..f869854
On Thu, May 24, 2018 at 06:59:36PM +0800, Tiwei Bie wrote:
> On Thu, May 24, 2018 at 10:24:40AM +0800, Tiwei Bie wrote:
> > On Thu, May 24, 2018 at 07:21:01AM +0800, Tiwei Bie wrote:
> > > On Wed, May 23, 2018 at 06:43:29PM +0300, Michael S. Tsirkin wrote:
> > > > On Wed, May 23, 2018 at 06:36:05PM
Hi Peter,
On 05/24/2018 04:16 PM, Peter Maydell wrote:
> On 24 May 2018 at 14:59, Auger Eric wrote:
>> Hi,
>>
>> On 05/24/2018 03:14 PM, Peter Maydell wrote:
>>> On 24 May 2018 at 10:04, Auger Eric wrote:
Now I am unclear about the semantics of the s->gicd_ipriority & friends.
With tha
On 24 May 2018 at 12:28, Su Hang wrote:
> This patch adds Intel Hexadecimal Object File format support to
> the loader. The file format specification is available here:
> http://www.piclist.com/techref/fileext/hex/intel.htm
>
> The file format is mainly intended for embedded systems
> and microco
On 24.05.2018 16:30, Michael S. Tsirkin wrote:
> Right now tests report OK status if QEMU crashes during cleanup.
> Let's catch that case and fail the test.
>
> Signed-off-by: Michael S. Tsirkin
> ---
> tests/libqtest.c | 9 -
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --
On Thu, May 24, 2018 at 04:55:04PM +0300, Michael S. Tsirkin wrote:
> On Thu, May 24, 2018 at 06:59:36PM +0800, Tiwei Bie wrote:
> > On Thu, May 24, 2018 at 10:24:40AM +0800, Tiwei Bie wrote:
> > > On Thu, May 24, 2018 at 07:21:01AM +0800, Tiwei Bie wrote:
> > > > On Wed, May 23, 2018 at 06:43:29PM
On Thu, May 24, 2018 at 04:48:09PM +0300, Michael S. Tsirkin wrote:
> On Thu, May 24, 2018 at 07:12:15AM +0800, Tiwei Bie wrote:
> > On Thu, May 24, 2018 at 12:25:23AM +0300, Michael S. Tsirkin wrote:
> > > On Thu, Apr 12, 2018 at 11:12:29PM +0800, Tiwei Bie wrote:
> > > > Signed-off-by: Tiwei Bie
On 24 May 2018 at 15:40, Auger Eric wrote:
> Hi Peter,
>
> On 05/24/2018 04:16 PM, Peter Maydell wrote:
>> Only for KVM, not for TCG, and it's the other way round: we
>> end up with two lots of PPI/SGI space in the data structure
>> by mistake. Let me fish out the comment I made on the v2 of this
On Thu, May 24, 2018 at 12:32:51PM +0100, Richard W.M. Jones wrote:
> There is however a seed of a good idea in the thread:
>
> > I don't think QEMU needs to use this information automatically,
> > necessarily. I think the first step is to simply make QEMU save
> > this information in the disk im
On 24 May 2018 at 15:56, Peter Maydell wrote:
> Oops, yes, you're right. My explanation applies to the
> various other bitmaps, where we are accessing the
> fields in the data structure using gic_bmp_ptr32(bmp, irq),
> but not to gicd_ipriority[], which we are directly accessing
> starting with th
On Thu, May 24, 2018 at 04:45:31PM +0200, Thomas Huth wrote:
> On 24.05.2018 16:30, Michael S. Tsirkin wrote:
> > Right now tests report OK status if QEMU crashes during cleanup.
> > Let's catch that case and fail the test.
> >
> > Signed-off-by: Michael S. Tsirkin
> > ---
> > tests/libqtest.c |
On 23 May 2018 at 13:09, Auger Eric wrote:
> Hi Igor,
>
> On 05/23/2018 12:22 PM, Igor Mammedov wrote:
>> When QEMU is started with following CLI
>> -machine virt,gic-version=3,accel=kvm -cpu host -bios AAVMF_CODE.fd
>> it crashes with abort at
>> accel/kvm/kvm-all.c:2164:
>> KVM_SET_DEVICE_ATT
On Thu, May 24, 2018 at 11:09:47AM +0200, Greg Kurz wrote:
> Removing a drive with drive_del while it is being used to run an I/O
> intensive workload can cause QEMU to crash.
>
> An AIO flush can yield at some point:
>
> blk_aio_flush_entry()
> blk_co_flush(blk)
> bdrv_co_flush(blk->root->bs)
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 1527086545-68024-1-git-send-email-...@redhat.com
Subject: [Qemu-devel] [PULL 00/28] pc, pci, virtio, vhost: fixes, features
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
n
Hi
On Thu, May 24, 2018 at 5:00 PM, Michael S. Tsirkin wrote:
> On Thu, May 24, 2018 at 04:45:31PM +0200, Thomas Huth wrote:
>> On 24.05.2018 16:30, Michael S. Tsirkin wrote:
>> > Right now tests report OK status if QEMU crashes during cleanup.
>> > Let's catch that case and fail the test.
>> >
>
1 - 100 of 250 matches
Mail list logo
