When I was reading 'qemu/hw/timer/m48t59.c'(Line:328) and run with
`make check-qtest-ppc`,
I found when write an invalid value 0xc to address 0x1FFF,
`from_bcd` return 12 instead of raising an exception(or error).
"""(qemu/hw/timer/m48t59.c)
case 0x1FFF:
case 0x07FF:
/* year */
Some backends report big max_io_sectors. Making min_io_size the same
value in this case will make it impossible for guest to align memory,
therefore the disk may not be usable at all.
Change the default behavior (when min_io_size and opt_io_size are not
specified in the command line), do not assum
I took a photo when SVM print reset.
It seems like kernel panic.
I hope this will help.
** Attachment added: "SVM_error.HEIC"
https://bugs.launchpad.net/qemu/+bug/1754542/+attachment/5086650/+files/SVM_error.HEIC
--
You received this bug notification because you are a member of qemu-
devel-
On Thu, 03/22 14:24, yuchen...@synology.com wrote:
> From: yuchenlin
>
> VMDK has a hard limitation of extent size, which is due to the size of grain
> table entry is 32 bits. It means it can only point to a grain located at
> offset = 2^32. To avoid writing the user data beyond limitation and re
On 22/3/18 2:29 am, Alex Williamson wrote:
> On Mon, 19 Mar 2018 21:49:58 +0100
> Auger Eric wrote:
>
>> Hi Alexey,
>>
>> On 09/02/18 08:55, Alexey Kardashevskiy wrote:
>>> At the moment if vfio_memory_listener is registered in the system memory
>>> address space, it maps/unmaps every RAM memory
Hi Yuval,
- Original Message -
> From: no-re...@patchew.org
> To: "yuval shaia"
> Cc: f...@redhat.com, "yuval shaia" ,
> mar...@redhat.com, ebl...@redhat.com,
> qemu-devel@nongnu.org, qemu-triv...@nongnu.org
> Sent: Thursday, March 22, 2018 7:07:35 AM
> Subject: Re: [Qemu-devel] [PATCH
Hi Alexey,
On 22/03/18 08:45, Alexey Kardashevskiy wrote:
> On 22/3/18 2:29 am, Alex Williamson wrote:
>> On Mon, 19 Mar 2018 21:49:58 +0100
>> Auger Eric wrote:
>>
>>> Hi Alexey,
>>>
>>> On 09/02/18 08:55, Alexey Kardashevskiy wrote:
At the moment if vfio_memory_listener is registered in th
SVM error photo
** Attachment removed: "SVM_error.HEIC"
https://bugs.launchpad.net/qemu/+bug/1754542/+attachment/5086650/+files/SVM_error.HEIC
** Attachment added: "SVM.err.jpg"
https://bugs.launchpad.net/qemu/+bug/1754542/+attachment/5086654/+files/SVM.err.jpg
--
You received this bug
On Wed, Mar 21, 2018 at 10:12:16PM -0500, Wei Huang wrote:
> Instead of using "1.0" as the system version of SMBIOS, we should use
> mc->desc for mach-virt machine type. With this patch, "dmidecode -t 1"
> (e.g., "-M virt-2.12,accel=kvm") will show:
>
> Handle 0x0100, DMI type 1, 27 bytes
>
Hi Peter,
This patch might be split in 2.
On 03/20/2018 02:41 PM, Peter Maydell wrote:
> When a debug exception is taken to AArch32, it appears as a Prefetch
> Abort, and the Instruction Fault Status Register (IFSR) must be set.
> The IFSR has two possible formats, depending on whether LPAE is in
On 03/19/2018 12:02 PM, Peter Maydell wrote:
> The BCM2836 uses a Cortex-A7, not a Cortex-A15. Update the device to
> use the correct CPU.
> https://www.raspberrypi.org/documentation/hardware/raspberrypi/bcm2836/QA7_rev3.4.pdf
>
> When the BCM2836 was introduced (bad5623690b) the Cortex-A7 was not
On 03/20/2018 02:41 PM, Peter Maydell wrote:
> For debug exceptions due to breakpoints or the BKPT instruction which
> are taken to AArch32, the Fault Address Register is architecturally
> UNKNOWN. We were using that as license to simply not set
> env->exception.vaddress, but this isn't correct, b
The 567b5b309abe ("vfio/pci: Relax DMA map errors for MMIO regions") added
an error message if a passed memory section address or size is not aligned
to the minimal IOMMU page size. However although it checks
offset_within_address_space for the alignment, offset_within_region is
printed instead whi
Hi Peter,
On 03/20/2018 02:41 PM, Peter Maydell wrote:
> The MDCR_EL2.TDE bit allows the exception level targeted by debug
> exceptions to be set to EL2 for code executing at EL0. We handle
> this in the arm_debug_target_el() function, but this is only used for
> hardware breakpoint and watchpoin
On 03/20/2018 10:41 AM, Peter Maydell wrote:
> Now that we have a helper function specifically for the BRK and
> BKPT instructions, we can set the exception.fsr there rather
> than in arm_cpu_do_interrupt_aarch32(). This allows us to
> use our new arm_debug_exception_fsr() helper.
>
> In particula
On 03/21/2018 06:10 PM, Yuval Shaia wrote:
> To avoid compilation warnings on 32-bit machines:
> rdma_backend.c: In function 'rdma_backend_create_mr':
> rdma_backend.c:409:37: error: cast to pointer from integer of different
> size [-Werror=int-to-pointer-cast]
> mr->ibmr = ibv_reg_mr(pd->ibp
On 03/21/2018 06:10 PM, Yuval Shaia wrote:
> Macro should not cast the given variable to u64 instead it should use
> the supplied format argument (fmt).
>
> Reported-by: Eric Blake
> Signed-off-by: Yuval Shaia
Reviewed-by: Philippe Mathieu-Daudé
> ---
> hw/rdma/rdma_backend.c | 4 ++--
> 1 f
> Hi, Howard,
>
> Thanks for reporting the problem. Could you try applying below patch
> to your rc0 tree and rebuild QEMU, to see whether it fixes your problem?
>
> -
> diff --git a/iothread.c b/iothread.c
> index 1b3463cb00..9f52270ae1 100644
> --- a/iothread.c
> +++
Hi Yuval,
On 03/21/2018 06:10 PM, Yuval Shaia wrote:
> Use the correct printf formats, so that a 32-bit compile doesn't spit
> out lots of warnings about %lx being incompatible with uint64_t.
>
> Suggested-by: Eric Blake
> Signed-off-by: Yuval Shaia
> ---
> hw/rdma/rdma_backend.c| 21 +
On 03/22/2018 12:47 AM, Fam Zheng wrote:
> The apt-get commands we run through ssh expect certain features of the
> tty, and refuses to work if /dev/null is used. It is ugly, but easy to
> satisfy.
>
> Actually, there is no reason to hide the output. It just makes things
> harder to diagnose. We c
On 03/06/2018 05:31 PM, Mark Cave-Ayland wrote:
> Introduce constants for the pre-defined New World IRQs to help keep things
> readable.
>
> Signed-off-by: Mark Cave-Ayland
> ---
> hw/ppc/mac.h | 8
> hw/ppc/mac_newworld.c | 29 +++--
> 2 files changed,
On Thu, Mar 22, 2018 at 09:28:34AM +0100, Howard Spoelstra wrote:
> > Hi, Howard,
> >
> > Thanks for reporting the problem. Could you try applying below patch
> > to your rc0 tree and rebuild QEMU, to see whether it fixes your problem?
> >
> > -
> > diff --git a/iothrea
Emilio G. Cota writes:
> For performance numbers see the last patch.
Just another random data point as we've been using himeno for our SVE
wor:
Master:
8:05:45 [alex@zen:~/l/q/qemu.git] master ± ./aarch64-linux-user/qemu-aarch64
sve.demo/himeno-v80
mimax = 129 mjmax = 65 mkmax = 65
imax =
OOB can enable iothread for parsing even on Windows. We need some tunes
to enable that on Windows otherwise it'll break Windows users. This
patch fixes the breakage on Windows with qemu-system-ppc.exe.
Reported-by: Howard Spoelstra
Tested-by: Howard Spoelstra
Suggested-by: Paolo Bonzini
Signe
On 22/03/2018 02:29, Emilio G. Cota wrote:
> It is indeed hard to see a large impact on performance given the
> large size of our critical sections. But hey, rcu_read_unlock
> goes down from 0.24% to 0.08% of execution time when booting
> aarch64 linux!
I expect something a little better than 0.15
Hi Mark,
On 03/21/2018 12:29 AM, David Gibson wrote:
> On Tue, Mar 06, 2018 at 08:31:01PM +, Mark Cave-Ayland wrote:
>> Commit 4e46dcdbd3 "PPC: Newworld: Add uninorth token register" added a TODO
>> which was to convert the uninorth registers hack to a proper device. Move
>> these registers to
* Stefan Berger (stef...@linux.vnet.ibm.com) wrote:
> On 03/21/2018 01:14 PM, Dr. David Alan Gilbert wrote:
> > * Stefan Berger (stef...@linux.vnet.ibm.com) wrote:
> > > +
> > > +if (totlength > 0) {
> > > +tsb->buffer = g_try_malloc(totlength);
> > > +if (!tsb->buffer) {
> > >
On 22/03/2018 08:38, Fam Zheng wrote:
> Some backends report big max_io_sectors. Making min_io_size the same
> value in this case will make it impossible for guest to align memory,
> therefore the disk may not be usable at all.
>
> Change the default behavior (when min_io_size and opt_io_size are
On 22/03/2018 08:03, Su Hang wrote:
> When I was reading 'qemu/hw/timer/m48t59.c'(Line:328) and run with
> `make check-qtest-ppc`,
> I found when write an invalid value 0xc to address 0x1FFF,
> `from_bcd` return 12 instead of raising an exception(or error).
Each device probably has a different beh
On 22/03/2018 09:56, Peter Xu wrote:
> OOB can enable iothread for parsing even on Windows. We need some tunes
> to enable that on Windows otherwise it'll break Windows users. This
> patch fixes the breakage on Windows with qemu-system-ppc.exe.
>
> Reported-by: Howard Spoelstra
> Tested-by: How
On 22/03/2018 06:19, Peter Xu wrote:
> +#ifdef CONFIG_LINUX
> /* Benchmark results from 2016 on NVMe SSD drives show max polling times
> around
> * 16-32 microseconds yield IOPS improvements for both iodepth=1 and
> iodepth=32
> * workloads.
> */
> #define IOTHREAD_POLL_MAX_NS_DEFAULT 327
Hi
On Thu, Mar 22, 2018 at 6:42 AM, Thomas Huth wrote:
> On 21.03.2018 12:52, Marc-André Lureau wrote:
>> Signed-off-by: Marc-André Lureau
>> Acked-by: Cornelia Huck
>> ---
>> qapi/misc.json | 101 --
>> qapi/target.json| 106
> >
>
> So many pr_err/pr_dbg() changes, you could have take the opportunity to
> replace with updated error reporting API and tracepoint.
Let's leave something for next time :)
>
> With %zu:
> Reviewed-by: Philippe Mathieu-Daudé
Thanks.
Hi all,
Following are three patches which fixes various compilation warnings and
errors detected when compiling rdma device in 32bit host.
All three patches are based on Eric Blake patch for rdma device.
Thanks!
Patch #1: Change host_virt to void *
Low level IB verbs library accept void * argumen
Macro should not cast the given variable to u64 instead it should use
the supplied format argument (fmt).
Reported-by: Eric Blake
Signed-off-by: Yuval Shaia
Reviewed-by: Eric Blake
Tested-by: Eric Blake
Reviewed-by: Philippe Mathieu-Daudé
---
hw/rdma/rdma_backend.c | 4 ++--
1 file changed,
To avoid compilation warnings on 32-bit machines:
rdma_backend.c: In function 'rdma_backend_create_mr':
rdma_backend.c:409:37: error: cast to pointer from integer of different
size [-Werror=int-to-pointer-cast]
mr->ibmr = ibv_reg_mr(pd->ibpd, (void *)addr, length, access);
Reported-by: Eri
Use the correct printf formats, so that a 32-bit compile doesn't spit
out lots of warnings about %lx being incompatible with uint64_t.
Suggested-by: Eric Blake
Signed-off-by: Yuval Shaia
Reviewed-by: Eric Blake
Tested-by: Eric Blake
Reviewed-by: Philippe Mathieu-Daudé
---
hw/rdma/rdma_backen
Hi Michael,
On 03/20/2018 07:25 PM, Michael Clark wrote:
> The following changes since commit f1a63fcfcd92c88be8942b5ae71aef9749a4f135:
>
> Update version for v2.12.0-rc0 release (2018-03-20 19:04:22 +)
>
> are available in the git repository at:
>
> https://github.com/riscv/riscv-qemu.
On Thu, Mar 22, 2018 at 10:14:19AM +0100, Paolo Bonzini wrote:
> On 22/03/2018 06:19, Peter Xu wrote:
> > +#ifdef CONFIG_LINUX
> > /* Benchmark results from 2016 on NVMe SSD drives show max polling times
> > around
> > * 16-32 microseconds yield IOPS improvements for both iodepth=1 and
> > iod
Hi
On Fri, Mar 9, 2018 at 10:00 AM, Peter Xu wrote:
> Having "allow-oob" to true for a command does not mean that this command
> will always be run in out-of-band mode. The out-of-band quick path will
> only be executed if we specify the extra "run-oob" flag when sending the
> QMP request:
>
>
Thanks for your reply. :-)
Su Hang
"Paolo Bonzini" wrote:
> On 22/03/2018 08:03, Su Hang wrote:
> > When I was reading 'qemu/hw/timer/m48t59.c'(Line:328) and run with
> > `make check-qtest-ppc`,
> > I found when write an invalid value 0xc to address 0x1FFF,
> > `from_bcd` return 12 instead of rai
Le 22/03/2018 à 02:52, Laurent Vivier a écrit :
> Le 23/01/2018 à 15:48, Laurent Vivier a écrit :
>> From: Peter Maydell
>>
>> If multiple guest threads in user-mode emulation write to a
>> page which QEMU has marked read-only because of cached TCG
>> translations, the threads can race in page_unp
On 22 March 2018 at 08:01, Andrew Jones wrote:
> I agree we should change the useless 1.0, but shouldn't we use
> mc->name instead of mc->desc? mc->name would make it consistent
> with pc-piix and q35 and also be a less verbose "version". We'd
> get e.g.
>
> System Information
> Manufactu
On 21 March 2018 at 22:26, Philippe Mathieu-Daudé wrote:
> Hi Peter,
>
> This patch might be split in 2.
For a +27-10 patch, it doesn't really seem necessary.
> On 03/20/2018 02:41 PM, Peter Maydell wrote:
>> When a debug exception is taken to AArch32, it appears as a Prefetch
>> Abort, and the
On 21 March 2018 at 22:29, Philippe Mathieu-Daudé wrote:
> On 03/20/2018 02:41 PM, Peter Maydell wrote:
>> For debug exceptions due to breakpoints or the BKPT instruction which
>> are taken to AArch32, the Fault Address Register is architecturally
>> UNKNOWN. We were using that as license to simp
On 22 March 2018 at 10:36, Laurent Vivier wrote:
> Le 22/03/2018 à 02:52, Laurent Vivier a écrit :
>> It seems this patch breaks something in linux-user mode emulation for
>> m68k (32bit BE) on ppc (32bit BE).
>>
>> What I have:
>>
>> ~/chroot$ sudo QEMU_CPU=m68040 chroot m68k/sid/
>> I have n
Le 22/03/2018 à 12:05, Peter Maydell a écrit :
> On 22 March 2018 at 10:36, Laurent Vivier wrote:
>> Le 22/03/2018 à 02:52, Laurent Vivier a écrit :
>>> It seems this patch breaks something in linux-user mode emulation for
>>> m68k (32bit BE) on ppc (32bit BE).
>>>
>>> What I have:
>>>
>>> ~/chr
On Wed, Mar 21, 2018 at 10:12:16PM -0500, Wei Huang wrote:
> Instead of using "1.0" as the system version of SMBIOS, we should use
> mc->desc for mach-virt machine type. With this patch, "dmidecode -t 1"
> (e.g., "-M virt-2.12,accel=kvm") will show:
>
> Handle 0x0100, DMI type 1, 27 bytes
>
On 22 March 2018 at 11:05, Peter Maydell wrote:
> On 22 March 2018 at 10:36, Laurent Vivier wrote:
>> It goes wrong in this part:
>>
>> + */
>> +if (is_write && info->si_signo == SIGSEGV && info->si_code ==
>> SEGV_ACCERR &&
>> +h2g_valid(address)) {
>>
>> Because, on ppc, si_code
On 22 March 2018 at 11:07, Laurent Vivier wrote:
> Le 22/03/2018 à 12:05, Peter Maydell a écrit :
>> On 22 March 2018 at 10:36, Laurent Vivier wrote:re.
>>> It goes wrong in this part:
>>>
>>> + */
>>> +if (is_write && info->si_signo == SIGSEGV && info->si_code ==
>>> SEGV_ACCERR &&
>>> +
Le 22/03/2018 à 12:07, Peter Maydell a écrit :
> On 22 March 2018 at 11:05, Peter Maydell wrote:
>> On 22 March 2018 at 10:36, Laurent Vivier wrote:
>>> It goes wrong in this part:
>>>
>>> + */
>>> +if (is_write && info->si_signo == SIGSEGV && info->si_code ==
>>> SEGV_ACCERR &&
>>> +
Signed-off-by: Alberto Garcia
Cc: Philippe Mathieu-Daudé
---
tests/qemu-iotests/186.out | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/qemu-iotests/186.out b/tests/qemu-iotests/186.out
index ec75c0fc60..5020162826 100644
--- a/tests/qemu-iotests/186.out
+++ b/tests
SCSI controllers are no longer created automatically for
-drive if=scsi, so this patch updates the tests that relied
on that.
Signed-off-by: Alberto Garcia
Reviewed-by: Eric Blake
Cc: Thomas Huth
---
tests/qemu-iotests/051.pc.out | 20
tests/qemu-iotests/186| 4 --
Hi,
I sent a patch a few days ago correction the output of iotests 051 and
186. I wanted to resend it again but I noticed that 186 needs now more
changes due to commit ac64273c66ab136c44043259162, so I'm including
those changes too.
Regards,
Berto
Alberto Garcia (2):
iotests: Update 051 and 1
On 03/21/2018 04:19 PM, Peter Xu wrote:
On Fri, Mar 16, 2018 at 04:05:14PM +0800, Xiao Guangrong wrote:
Hi David,
Thanks for your review.
On 03/15/2018 06:25 PM, Dr. David Alan Gilbert wrote:
migration/ram.c | 32
Hi,
Do you have some performance n
On 03/21/2018 05:06 PM, Peter Xu wrote:
On Tue, Mar 13, 2018 at 03:57:33PM +0800, guangrong.x...@gmail.com wrote:
From: Xiao Guangrong
Current code uses compress2()/uncompress() to compress/decompress
memory, these two function manager memory allocation and release
internally, that causes hu
On Wed, Mar 21, 2018 at 2:19 AM, Juan Quintela wrote:
> Lidong Chen wrote:
>> RDMA migration implement save_page function for QEMUFile, but
>> ram_control_save_page do not increase bytes_xfer. So when doing
>> RDMA migration, it will use whole bandwidth.
>>
>> Signed-off-by: Lidong Chen
>
> Revi
Hi
On Fri, Mar 9, 2018 at 10:00 AM, Peter Xu wrote:
> For those monitors who have enabled IO thread, we'll offload the
> responding procedure into IO thread. The main reason is that chardev is
> not thread safe, and we need to do all the read/write IOs in the same
> thread. For use_io_thr=true
On 03/21/2018 06:00 PM, Peter Xu wrote:
On Tue, Mar 13, 2018 at 03:57:34PM +0800, guangrong.x...@gmail.com wrote:
From: Xiao Guangrong
Currently the page being compressed is allowed to be updated by
the VM on the source QEMU, correspondingly the destination QEMU
just ignores the decompressio
On 20 March 2018 at 20:43, Laurent Vivier wrote:
> The following changes since commit 036793aebfc1dd0ce124fa278d7668d89b5da936:
>
> Merge remote-tracking branch
> 'remotes/ehabkost/tags/machine-next-pull-request' into staging (2018-03-20
> 12:56:20 +)
>
> are available in the Git repositor
Hi,
On 03/22/2018 04:38 AM, Fam Zheng wrote:
Some backends report big max_io_sectors. Making min_io_size the same
value in this case will make it impossible for guest to align memory,
therefore the disk may not be usable at all.
Change the default behavior (when min_io_size and opt_io_size are
L2 entries for compressed clusters have a field that indicates the
number of sectors used to store the data in the image.
That's however not the size of the compressed data itself, just the
number of sectors where that data is located. The actual data size is
usually not a multiple of the sector s
Ping for code review -- it would be nice to put this bugfix
into rc1.
thanks
-- PMM
On 15 March 2018 at 13:34, Peter Maydell wrote:
> If the GIC has the security extension support enabled, then a
> non-secure access to ICC_PMR must take account of the non-secure
> view of interrupt priorities, w
On 03/21/2018 09:40 PM, yuchenlin--- via Qemu-devel wrote:
From: yuchenlin
VMDK has a hard limitation of extent size, which is due to the size of grain
table entry is 32 bits. It means it can only point to a grain located at
offset = 2^32. To prevent offset overflow and record a useless offset
On Wed, Mar 21, 2018 at 05:19:24PM -0300, Eduardo Habkost wrote:
> On Wed, Mar 21, 2018 at 07:57:29PM +0300, Roman Kagan wrote:
> > On Wed, Mar 21, 2018 at 02:18:54PM +0100, Vitaly Kuznetsov wrote:
> > > Roman Kagan writes:
> > >
> > > > On Tue, Mar 20, 2018 at 06:35:00PM +0100, Vitaly Kuznetsov
On 03/21/2018 10:47 PM, Fam Zheng wrote:
The apt-get commands we run through ssh expect certain features of the
tty, and refuses to work if /dev/null is used. It is ugly, but easy to
satisfy.
Actually, there is no reason to hide the output. It just makes things
harder to diagnose. We can always
On 03/22/2018 02:41 AM, Fam Zheng wrote:
On Thu, 03/22 14:24, yuchen...@synology.com wrote:
From: yuchenlin
VMDK has a hard limitation of extent size, which is due to the size of grain
table entry is 32 bits. It means it can only point to a grain located at
offset = 2^32. To avoid writing the
Changes since v3:
- check cpu->hyperv_reenlightenment instead of has_msr_reenlightenment
[Eduardo Habkost, Roman Kagan]
- expose frequency MSRs only when either INVTSC or Reenlightenment is
provided [Paolo Bonzini] (I'm not doing 'hv_frequency' property for now
as the discussion around it see
We can also expose Hyper-V frequency MSRs when reenlightenment feature is
enabled and TSC frequency is known, Hyper-V on KVM will provide stable TSC
page clocksources to its guests.
Signed-off-by: Vitaly Kuznetsov
---
- Expose frequency MSRs only when either INVTSC or Reenlightenment is
provide
On 21 March 2018 at 12:07, Stefan Berger wrote:
> This series of patches fixes the initialization and setting of a few
> flags of the TPM CRB interface.
>
> The following changes since commit f1a63fcfcd92c88be8942b5ae71aef9749a4f135:
>
> Update version for v2.12.0-rc0 release (2018-03-20 19:04:2
KVM recently gained support for Hyper-V Reenlightenment MSRs which are
required to make KVM-on-Hyper-V enable TSC page clocksource to its guests
when INVTSC is not passed to it (and it is not passed by default in Qemu
as it effectively blocks migration).
Signed-off-by: Vitaly Kuznetsov
---
Change
On 03/22/2018 06:14 AM, Alberto Garcia wrote:
Signed-off-by: Alberto Garcia
Cc: Philippe Mathieu-Daudé
---
tests/qemu-iotests/186.out | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/qemu-iotests/186.out b/tests/qemu-iotests/186.out
index ec75c0fc60..5020162826 1
On Thu, Mar 22, 2018 at 04:00:14PM +0300, Roman Kagan wrote:
> On Wed, Mar 21, 2018 at 05:19:24PM -0300, Eduardo Habkost wrote:
> > On Wed, Mar 21, 2018 at 07:57:29PM +0300, Roman Kagan wrote:
> > > On Wed, Mar 21, 2018 at 02:18:54PM +0100, Vitaly Kuznetsov wrote:
> > > > Roman Kagan writes:
> > >
On 03/22/2018 12:00 AM, Peter Xu wrote:
Doesn't OOB insist on having an ID field with the command?
OOB insists on an id field - but there is the situation that SOME errors
occur even before the id field has been encountered (for example, if you
send non-JSON, the parser gets all confused - it
From: yuchenlin
VMDK has a hard limitation of extent size, which is due to the size of grain
table entry is 32 bits. It means it can only point to a grain located at
offset = 2^32. To avoid writing the user data beyond limitation and record a
useless offset
in grain table. We should return ERROR
On Thu 22 Mar 2018 02:17:23 PM CET, Eric Blake wrote:
>> --- a/tests/qemu-iotests/186.out
>> +++ b/tests/qemu-iotests/186.out
>> @@ -404,7 +404,7 @@ Testing: -drive if=floppy
>> QEMU X.Y.Z monitor - type 'help' for more information
>> (qemu) info block
>> floppy0: [not inserted]
>> -Attac
On 03/22/2018 05:53 AM, Peter Maydell wrote:
> On 22 March 2018 at 08:01, Andrew Jones wrote:
>> I agree we should change the useless 1.0, but shouldn't we use
>> mc->name instead of mc->desc? mc->name would make it consistent
>> with pc-piix and q35 and also be a less verbose "version". We'd
>>
On Thu, Mar 22, 2018 at 11:07:12AM +, Daniel P. Berrangé wrote:
> On Wed, Mar 21, 2018 at 10:12:16PM -0500, Wei Huang wrote:
> > Instead of using "1.0" as the system version of SMBIOS, we should use
> > mc->desc for mach-virt machine type. With this patch, "dmidecode -t 1"
> > (e.g., "-M virt-2
On Wed, Mar 21, 2018 at 05:58:48PM -0400, John Snow wrote:
> ./check -v -raw
> Failures: 109 132 136 148 152 183
>
> 3fd2457d18edf5736f713dfe1ada9c87a9badab1 is the first bad commit
> commit 3fd2457d18edf5736f713dfe1ada9c87a9badab1
> Author: Peter Xu
> Date: Fri Mar 9 17:00:03 2018 +0800
>
>
On 03/22/2018 08:42 AM, Alberto Garcia wrote:
On Thu 22 Mar 2018 02:17:23 PM CET, Eric Blake wrote:
--- a/tests/qemu-iotests/186.out
+++ b/tests/qemu-iotests/186.out
@@ -404,7 +404,7 @@ Testing: -drive if=floppy
QEMU X.Y.Z monitor - type 'help' for more information
(qemu) info block
flo
On Thu, Mar 22, 2018 at 02:49:35PM +0100, Andrew Jones wrote:
> On Thu, Mar 22, 2018 at 11:07:12AM +, Daniel P. Berrangé wrote:
> > On Wed, Mar 21, 2018 at 10:12:16PM -0500, Wei Huang wrote:
> > > Instead of using "1.0" as the system version of SMBIOS, we should use
> > > mc->desc for mach-virt
On Thu, Mar 22, 2018 at 10:22:18AM -0300, Eduardo Habkost wrote:
> On Thu, Mar 22, 2018 at 04:00:14PM +0300, Roman Kagan wrote:
> > On Wed, Mar 21, 2018 at 05:19:24PM -0300, Eduardo Habkost wrote:
> > > On Wed, Mar 21, 2018 at 07:57:29PM +0300, Roman Kagan wrote:
> > > > On Wed, Mar 21, 2018 at 02:
On 21 March 2018 at 14:37, Marc-André Lureau
wrote:
> The following changes since commit f1a63fcfcd92c88be8942b5ae71aef9749a4f135:
>
> Update version for v2.12.0-rc0 release (2018-03-20 19:04:22 +)
>
> are available in the Git repository at:
>
> https://github.com/elmarco/qemu.git tags/dum
On Thu, Mar 15, 2018 at 01:34:41PM +, Peter Maydell wrote:
> If the GIC has the security extension support enabled, then a
> non-secure access to ICC_PMR must take account of the non-secure
> view of interrupt priorities, where real priorities 0..0x7f
> are secure-only and not visible to the no
21.03.2018 17:56, Eric Blake wrote:
[adding NBD list]
On 03/21/2018 07:19 AM, Vladimir Sementsov-Ogievskiy wrote:
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
nbd/server.c | 60
+++-
1 file changed, 43 insertions(+), 17 deletions(
Hi,
I sent a patch a few days ago correction the output of iotests 051 and
186. I wanted to resend it again but I noticed that 186 needs now more
changes due to commit ac64273c66ab136c44043259162, so I'm including
those changes too.
Regards,
Berto
v4: Filter 'Attached to:' lines [Eric]
Alberto
SCSI controllers are no longer created automatically for
-drive if=scsi, so this patch updates the tests that relied
on that.
Signed-off-by: Alberto Garcia
Reviewed-by: Eric Blake
Cc: Thomas Huth
---
tests/qemu-iotests/051.pc.out | 20
tests/qemu-iotests/186| 4 --
Commit ac64273c66ab136c44 modified the output of iotest 186, changing
the QOM path of floppy drives from /machine/unattached/device[17] to
/machine/unattached/device[13].
Instead of updating the test output to reflect this change, this patch
adds a new filter that hides all QOM paths from the 'Att
On Mon, Mar 19, 2018 at 03:15:31PM +0800, Tiwei Bie wrote:
> This patch set does some small extensions to vhost-user protocol
> to support VFIO based accelerators, and makes it possible to get
> the similar performance of VFIO based PCI passthru while keeping
> the virtio device emulation in QEMU.
On Mon, Mar 19, 2018 at 03:15:34PM +0800, Tiwei Bie wrote:
> Provide APIs to support querying whether the page-per-vq
> is enabled and adding sub-regions for notify region.
>
> Signed-off-by: Tiwei Bie
> ---
> Makefile.target| 4
> hw/virtio/virtio-pci.c | 48
> +++
On Thu, Mar 22, 2018 at 14:41:05 +0800, Richard Henderson wrote:
> On 03/22/2018 01:57 PM, Emilio G. Cota wrote:
> >> Is there any especially good reason you want to not put this code into the
> >> normal softfloat function? Does it really many any measurable difference
> >> at
> >> all to force
ping
http://patchwork.ozlabs.org/project/qemu-devel/list/?series=33714
Le 22/03/2018 à 16:08, Emilio G. Cota a écrit :
> On Thu, Mar 22, 2018 at 14:41:05 +0800, Richard Henderson wrote:
>> On 03/22/2018 01:57 PM, Emilio G. Cota wrote:
Is there any especially good reason you want to not put this code into the
normal softfloat function? Does it really many an
On 22 March 2018 at 15:08, Abdallah Bouassida
wrote:
> ping
> http://patchwork.ozlabs.org/project/qemu-devel/list/?series=33714
Hi. This patchset is on my to-review queue, but it may take me
a little while to get back to it because we're currently in
freeze for the 2.12 release and so things that
On Mon, Mar 19, 2018 at 03:15:33PM +0800, Tiwei Bie wrote:
> @@ -22,7 +23,7 @@
>
> typedef struct VhostUserState {
> NetClientState nc;
> -CharBackend chr; /* only queue index 0 */
> +VhostUser vhost_user; /* only queue index 0 */
> VHostNetState *vhost_net;
> guint watch;
On Mon, Mar 19, 2018 at 03:15:36PM +0800, Tiwei Bie wrote:
> This macro isn't used by any VFIO code. And its name is
> too generic. The vfio-common.h (in include/hw/vfio) can
> be included by other modules in QEMU. It can introduce
> conflicts.
>
> Signed-off-by: Tiwei Bie
This one can go ahead
21.03.2018 19:57, Eric Blake wrote:
On 03/21/2018 07:19 AM, Vladimir Sementsov-Ogievskiy wrote:
Signed-off-by: Vladimir Sementsov-Ogievskiy
Rather sparse on the details in the commit message; I had to read the
patch to even learn what the new namespace is.
oh, yes, sorry :(
@@ -92,6 +101
On Thu, Mar 22, 2018 at 08:56:36 +, Alex Bennée wrote:
>
> Emilio G. Cota writes:
>
>
> > For performance numbers see the last patch.
>
> Just another random data point as we've been using himeno for our SVE
> wor:
>
> Master:
>
> 8:05:45 [alex@zen:~/l/q/qemu.git] master ± ./aarch64-lin
qemu_aio_coroutine_enter() is (indirectly) called recursively when
processing co_queue_wakeup. This can lead to stack exhaustion.
This patch rewrites co_queue_wakeup in an iterative fashion (instead of
recursive) with bounded memory usage to prevent stack exhaustion.
qemu_co_queue_run_restart()
co_queue_wakeup is currently implemented in a recursive fashion. Pathological
patterns of aio_co_enter() between coroutines can cause stack exhaustion.
This patch series implements co_queue_wakeup iteratively and avoids stack
exhaustion.
This issue was originally reported with qemu-img convert b
1 - 100 of 198 matches
Mail list logo
