>> +/*
>> + * Other VIO devices register values, when allocated by
>> + * livirt, are mapped in range [0x00 - 0xef].
>> + */
>> +irq = (reg >> 12) & 0xef;
>
> This mask doesn't do what you intend - it will map 0x10 to 0, for
oops. yes indeed.
> example. Y
Cc: qemu-sta...@nongnu.org
Signed-off-by: Fam Zheng
---
block/file-posix.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/block/file-posix.c b/block/file-posix.c
index ad299beb38..928b863ced 100644
--- a/block/file-posix.c
+++ b/block/file-posix.c
@@ -1646,6 +1646,9 @@ static int handle_a
On 07/26/2018 10:56 PM, Richard Henderson wrote:
On 07/25/2018 11:48 PM, Shivaprasad G Bhat wrote:
Reference:
https://refspecs.linuxfoundation.org/ELF/ppc64/PPC-elf64abi-1.9.html#REG
This document is for _CALL_ELF < 2. For ppc64le, the document is at
https://openpowerfoundation.org/wp-cont
On 26 July 2018 at 20:43, Peter Maydell wrote:
> On 26 July 2018 at 13:35, Andrew Jones wrote:
>> On Thu, Jul 26, 2018 at 01:10:34PM +0100, Peter Maydell wrote:
>>> On 26 July 2018 at 12:41, Andrew Jones wrote:
>>> > The patch guards the generation. It'll only modify DT and ACPI for the
>>> > ne
This is based on liujunjie's "[PATCH] qstring: Fix
qstring_from_substr() not to provoke int overflow". I intend to get
that one into 3.0 as a bug fix. I figure PATCH 1 should go into 3.0
as a safety measure. I'm leaning towards including PATCH 2 as well.
Based-on: 20180724134339.17832-1-liujunj
qstring_from_substr() takes the index of the substring's first and
last character. qstring_from_substr(s, 0, SIZE_MAX) denotes an empty
substring. Awkward.
Shift the end index one to the right. This simplifies both
qstring_from_substr() and its callers.
Signed-off-by: Markus Armbruster
Review
Signed-off-by: Markus Armbruster
---
qobject/qstring.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/qobject/qstring.c b/qobject/qstring.c
index 18b8eb82f8..1bb7784a88 100644
--- a/qobject/qstring.c
+++ b/qobject/qstring.c
@@ -41,17 +41,19 @@ QString *qstring_from_subst
On Thu, Jul 26, 2018 at 10:20:11PM -0700, Richard Henderson wrote:
> On 07/26/2018 08:13 PM, David Gibson wrote:
> > On Thu, Jul 26, 2018 at 01:56:19PM +0530, Shivaprasad G Bhat wrote:
> >> r11 is a volatile register on PPC as per calling conventions.
> >> The safe_syscall code uses it to check if
Hi Cleber,
On 06/28/2018 07:03 PM, Philippe Mathieu-Daudé wrote:
> On 06/28/2018 06:54 PM, Alex Bennée wrote:
>> Alex Bennée writes:
>>> Philippe Mathieu-Daudé writes:
>>>
Tests can change this property to run tests in other
architectures than the host one.
Signed-off-by: Phi
On Mon, Jul 23, 2018 at 10:54 PM, Gal Shachaf wrote:
> On Thu, Jul 5, 2018 at 10:26 PM, 858585 jemmy wrote:
>> On Thu, Jun 28, 2018 at 2:59 AM, Dr. David Alan Gilbert
>> wrote:
>>> * Lidong Chen (jemmy858...@gmail.com) wrote:
ibv_dereg_mr wait for a long time for big memory size virtual ser
Hi Alex,
On 06/28/2018 01:01 PM, Alex Bennée wrote:
> Philippe Mathieu-Daudé writes:
>>
>> Another neanderthal approach to add multi-arch acceptance tests using
>> Avocado.
>>
>> Since Cleber Rosa work got merged [0], I can restart my previous attempt [1]
>> at using Avocado in QEMU.
>> Cleber Ro
On Tue, Jul 24, 2018 at 02:18:30PM +0200, Cédric Le Goater wrote:
> Hello,
>
> >From the discussion on the XICS MSI object, I gather that exporting
> icp_irq is fine.
>
> Some more comments below, I have tried to answer the parts that were
> not addressed yet.
[snip]
> > Could you use memory_r
On Wed, Jul 25, 2018 at 04:45:26PM +0200, Greg Kurz wrote:
> Commit b585395b655 fixed a regression introduced by some recent changes
> in the XICS code, that was causing QEMU to crash instantly during CPU
> hotplug with KVM. This is typically the kind of bug we'd like our
> test suite to detect bef
Hi Stefan,
On 07/25/2018 05:59 AM, Stefan Hajnoczi wrote:
> Define a "cortex-m0" ARMv6-M CPU model.
>
> Most of the register reset values set by other CPU models are not
> relevant for the cut-down ARMv6-M architecture.
>
> Signed-off-by: Stefan Hajnoczi
> ---
> target/arm/cpu.c | 11 +
On 07/26/2018 08:13 PM, David Gibson wrote:
> On Thu, Jul 26, 2018 at 01:56:19PM +0530, Shivaprasad G Bhat wrote:
>> r11 is a volatile register on PPC as per calling conventions.
>> The safe_syscall code uses it to check if the signal_pending
>> is set during the safe_syscall. When a syscall is int
On Thu, Jul 26, 2018 at 03:37:22PM +0200, Cédric Le Goater wrote:
> This proposal moves all the related IRQ routines of the sPAPR machine
> behind a sPAPR IRQ backend interface 'spapr_irq' to prepare for future
> changes. First of which will be to increase the size of the IRQ number
> space, then,
On 07/25/2018 05:59 AM, Stefan Hajnoczi wrote:
> ARMv6-M and ARMv8-M need the same kernel loading functionality as
> ARMv7-M. Rename armv7m_load_kernel() to arm_m_profile_load_kernel() so
> it's clear that this function isn't specific to ARMv7-M.
>
> Signed-off-by: Stefan Hajnoczi
Reviewed-by:
On 07/25/2018 05:59 AM, Stefan Hajnoczi wrote:
> Some ARM CPUs have bitbanded IO, a memory region that allows convenient
> bit access via 32-bit memory loads/stores. This eliminates the need for
> read-modify-update instruction sequences.
>
> This patch makes this optional feature a ARMMProfile q
On 07/25/2018 05:59 AM, Stefan Hajnoczi wrote:
> The TYPE_ARMV7M class is really a container for an ARM M Profile CPU,
> NVIC, and related pieces. It can also be used for ARMv6-M and ARMv8-M.
> Rename the class since it is not exclusive to ARMv7-M.
>
> Signed-off-by: Stefan Hajnoczi
Reviewed-by
> From: Alex Bennée [mailto:alex.ben...@linaro.org]
> > Replay is capable of recording normal BH events, but sometimes
> > there are single use callbacks scheduled with aio_bh_schedule_oneshot
> > function. This patch enables recording and replaying such callbacks.
> > Block layer uses these events
Hi Su,
On 07/25/2018 05:59 AM, Stefan Hajnoczi wrote:
> From: Su Hang
>
> '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 binar
On 07/26/2018 10:39 AM, Laurent Vivier wrote:
> Le 26/07/2018 à 19:15, Richard Henderson a écrit :
>> On 07/25/2018 11:48 PM, Shivaprasad G Bhat wrote:
>>> r11 is a volatile register on PPC as per calling conventions.
>>> The safe_syscall code uses it to check if the signal_pending
>>> is set durin
On Thu, Jul 26, 2018 at 03:37:21PM +0200, Cédric Le Goater wrote:
> This proposal introduces a new IRQ number space layout using static
> numbers for all devices, depending on a device index, and a bitmap
> allocator for the MSI IRQ numbers which are negotiated by the guest at
> runtime.
>
> As th
On Thu, Jul 26, 2018 at 01:56:19PM +0530, Shivaprasad G Bhat wrote:
> r11 is a volatile register on PPC as per calling conventions.
> The safe_syscall code uses it to check if the signal_pending
> is set during the safe_syscall. When a syscall is interrupted
> on return from signal handling, the r1
Signed-off-by: Fam Zheng
---
tests/qemu-iotests/082 | 8
tests/qemu-iotests/082.out | 11 +++
2 files changed, 19 insertions(+)
diff --git a/tests/qemu-iotests/082 b/tests/qemu-iotests/082
index a872f771a6..3e605d52d1 100755
--- a/tests/qemu-iotests/082
+++ b/tests/qemu-iot
This reverts commit eb461485f4558e362fab905735b50987505bca44.
Now that we introduce an explicit option, these implicit rules are not
used.
Signed-off-by: Fam Zheng
---
qemu-img.texi | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/qemu-img.texi b/qemu-img.texi
index 585
Signed-off-by: Fam Zheng
---
qemu-img-cmds.hx | 2 +-
qemu-img.c | 21 +
qemu-img.texi| 8 +++-
3 files changed, 25 insertions(+), 6 deletions(-)
diff --git a/qemu-img-cmds.hx b/qemu-img-cmds.hx
index 69758fb6e8..1526f327a5 100644
--- a/qemu-img-cmds.hx
+++ b/
Kevin pointed out that both glibc and kernel provides a slow fallback of
copy_file_range which hurts thin provisioning. This is particularly true for
thin LVs, because host_device driver cannot get allocation info from the
volume, and copy_file_range is called on every sectors, making the dst fully
On Thu, Jul 26, 2018 at 02:45:39PM -0600, Alex Williamson wrote:
> On Mon, 23 Jul 2018 12:59:56 +0800
> Tiwei Bie wrote:
>
[...]
> >
> > +static int vhost_user_slave_handle_vfio_group(struct vhost_dev *dev,
> > + int *fd)
> > +{
> > +struct vhost
On Thu, Jul 26, 2018 at 09:44:11AM +0200, Laurent Vivier wrote:
> On 26/07/2018 07:07, David Gibson wrote:
> > On Thu, May 03, 2018 at 11:20:44PM -0500, Michael Roth wrote:
> >> In some cases (e.g. spapr) we record guest timebase after qmp_stop()
> >> via a runstate hook so we can restore it on qmp
On Thu, Jul 26, 2018 at 07:30:34AM -0500, Michael Roth wrote:
> Quoting David Gibson (2018-07-26 00:07:46)
> > On Thu, May 03, 2018 at 11:20:44PM -0500, Michael Roth wrote:
> > > In some cases (e.g. spapr) we record guest timebase after qmp_stop()
> > > via a runstate hook so we can restore it on q
On 2018/7/27 0:55, Halil Pasic wrote:
> Sorry I did not have any time for this last days. And this
> to make it worse this is a follow up to something that was
> half a year ago. That means I have to re-familiarize myself
> with the topic.
>
> If I don't get around to answer in couple of weeks
On Thu, Jul 26, 2018 at 04:44:43PM -0300, Yasmin Beatriz wrote:
> On Thu, Jul 26, 2018 at 11:40:20AM +1000, David Gibson wrote:
> > On Tue, Jul 24, 2018 at 12:13:04PM +, Yasmin Beatriz wrote:
> > > After solving a corner case in bcdsub, this patch simplifies the logic
> > > of both bcdadd/sub i
When scanout_mode enabled, surface is out of sync with actual screen.
In such case, we just call sdl2_gl_scanout_flush to do redraw. This
fixes bug reported in
https://lists.freedesktop.org/archives/virglrenderer-devel/2018-July/001330.html
Signed-off-by: Tao Wu
---
ui/sdl2-gl.c | 5 +
1 fil
On Thu, 2018-07-26 at 11:03 +0200, Cédric Le Goater wrote:
> Ben,
>
> I have found out recently that the QEMU PowerNV could hang while accessing
> the disk.
>
> The issue seems to be the phb3_msi_try_send() routine when called from
> the resend() handler. The 'P' is ignored in that case but not
On 07/27/2018 12:28 AM, Kevin Wolf wrote>
That makes sense. You probably need to clone the QDict before passing
it to qcow2_update_options(), with qdict_clone_shallow().
Sounds like a solution! Great, thanks!
Can QAPI be the solution? I've seen some examples, and it looks like
the
qcow2 dri
Am 26.07.2018 um 23:08 hat Leonid Bloch geschrieben:
> On July 26, 2018 11:19:03 PM EEST, Kevin Wolf wrote:
> >Am 26.07.2018 um 21:43 hat Leonid Bloch geschrieben:
> >> On 07/26/2018 05:50 PM, Leonid Bloch wrote:
> >> > On 07/26/2018 05:42 PM, Kevin Wolf wrote:
> >> > > Am 26.07.2018 um 14:24 hat
On July 26, 2018 11:19:03 PM EEST, Kevin Wolf wrote:
>Am 26.07.2018 um 21:43 hat Leonid Bloch geschrieben:
>> On 07/26/2018 05:50 PM, Leonid Bloch wrote:
>> > On 07/26/2018 05:42 PM, Kevin Wolf wrote:
>> > > Am 26.07.2018 um 14:24 hat Leonid Bloch geschrieben:
>> > > > > > You mean with QDict?
On Mon, 23 Jul 2018 12:59:56 +0800
Tiwei Bie wrote:
> Introduce a slave message to allow slave to share its
> VFIO group fd to master and do the IOMMU programming
> based on virtio device's DMA address space for this
> group in QEMU.
>
> For the vhost backends which support vDPA, they could
> le
Whoops.. Forgot to include the QEMU command line:
qemu-system-aarch64 -M raspi3 --kernel kernel8.img -serial stdio
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1777672
Title:
QEMU aarch64 virtual
Certainly! Attached.
If you start the attached on a piece of hardware, it will start and display
fine.. If you start it in QEMU, it will start but display a double-height
screen rather than limiting the physical screen to the specified dimensions.
(The virtual display is double-height in prep
Am 26.07.2018 um 21:43 hat Leonid Bloch geschrieben:
> On 07/26/2018 05:50 PM, Leonid Bloch wrote:
> > On 07/26/2018 05:42 PM, Kevin Wolf wrote:
> > > Am 26.07.2018 um 14:24 hat Leonid Bloch geschrieben:
> > > > > > You mean with QDict? I'll look into that now. But
> > > > > > already sent v5 befor
On Thu, Jul 26, 2018 at 11:40:20AM +1000, David Gibson wrote:
> On Tue, Jul 24, 2018 at 12:13:04PM +, Yasmin Beatriz wrote:
> > After solving a corner case in bcdsub, this patch simplifies the logic
> > of both bcdadd/sub instructions by removing some unnecessary local flags.
> >
> > Signed-of
On 07/26/2018 05:50 PM, Leonid Bloch wrote:
On 07/26/2018 05:42 PM, Kevin Wolf wrote:
Am 26.07.2018 um 14:24 hat Leonid Bloch geschrieben:
You mean with QDict? I'll look into that now. But already sent v5
before
reading this email.
Yes, with reading it from the QDict. (Or whatever the simple
Will do, thanks!
On Thu, 26 Jul 2018 at 19:12, Laurent Vivier wrote:
> Le 26/07/2018 à 19:58, Alex Bennée a écrit :
> >
> > Laurent Vivier writes:
> >
> >> Le 26/07/2018 à 15:29, Alex Bennée a écrit:
> >>> I've slightly re-organised the check to more closely match the
> >>> sequence that the ke
On 07/26/2018 10:23 AM, Eric Blake wrote:
Hmm - that thread also mentions FALLOC_FL_NO_HIDE_STALE, which is a new
flag not present/documented on Fedora 28. I wonder if it helps, too.
Even more odd - that flag has been proposed to the kernel since 2012 but
still not mentioned in the F28 man
Le 26/07/2018 à 19:58, Alex Bennée a écrit :
>
> Laurent Vivier writes:
>
>> Le 26/07/2018 à 15:29, Alex Bennée a écrit:
>>> I've slightly re-organised the check to more closely match the
>>> sequence that the kernel uses in do_mmap().
>>>
>>> Signed-off-by: Alex Bennée
>>> Cc: umarcor <1783...
Am 26.07.2018 um 19:34 hat Nir Soffer geschrieben:
> On Thu, Jul 26, 2018 at 7:58 PM Kevin Wolf wrote:
> > Am 26.07.2018 um 18:46 hat Nir Soffer geschrieben:
> > > I don't think we should depend on undocumented kernel code.
> >
> > Yes, the man page says "filesystem blocks" instead of just "blocks
On 07/26/2018 12:34 PM, Nir Soffer wrote:
Anyway this looks the same level of documentation as FALLOC_FL_ZERO_RANGE,
so if we are ok with using it, FALLOC_FL_PUNCH_HOLE is fine.
Does this change mean that oVirt can start to enable discard for VM when
disks are using wipe-after-delete?
Current
Laurent Vivier writes:
> Le 26/07/2018 à 15:29, Alex Bennée a écrit:
>> I've slightly re-organised the check to more closely match the
>> sequence that the kernel uses in do_mmap().
>>
>> Signed-off-by: Alex Bennée
>> Cc: umarcor <1783...@bugs.launchpad.net>
>> ---
>> linux-user/mmap.c | 14 +
On Wed, Jul 25, 2018 at 04:39:28PM +0200, Igor Mammedov wrote:
> > > > +void cst_register(FWCfgState *s, uint16_t ioport)
> > > > +{
> > > > +cst_ssdt_setup();
> > > > +
> > > > +/* Allocate guest scratch memory for the table */
> > > > +cst_scratch = g_array_new(false, true, 1);
> > >
Le 26/07/2018 à 19:15, Richard Henderson a écrit :
> On 07/25/2018 11:48 PM, Shivaprasad G Bhat wrote:
>> r11 is a volatile register on PPC as per calling conventions.
>> The safe_syscall code uses it to check if the signal_pending
>> is set during the safe_syscall. When a syscall is interrupted
>>
On Thu, Jul 26, 2018 at 7:58 PM Kevin Wolf wrote:
> Am 26.07.2018 um 18:46 hat Nir Soffer geschrieben:
> > On Thu, Jul 26, 2018 at 7:10 PM Eric Blake wrote:
> >
> > > On 07/26/2018 10:33 AM, Kevin Wolf wrote:
> > >
> > > >
> > > > As far as I know, the comment you quoted is accurate for BLKDISCA
On Thu, Jul 26, 2018 at 06:42:51PM +0200, Knut Omang wrote:
> On Thu, 2018-07-26 at 19:41 +0300, Michael S. Tsirkin wrote:
> > On Thu, Jul 26, 2018 at 06:38:32PM +0200, Knut Omang wrote:
> > > On Thu, 2018-07-26 at 18:51 +0300, Marcel Apfelbaum wrote:
> > > > Hi
> > > >
> > > > On 07/26/2018 05:52
On Thu, 2018-07-26 at 20:05 +0300, Marcel Apfelbaum wrote:
>
> On 07/26/2018 07:42 PM, Knut Omang wrote:
> > On Thu, 2018-07-26 at 19:41 +0300, Michael S. Tsirkin wrote:
> > > On Thu, Jul 26, 2018 at 06:38:32PM +0200, Knut Omang wrote:
> > > > On Thu, 2018-07-26 at 18:51 +0300, Marcel Apfelbaum wr
On Thu, 2018-07-26 at 20:05 +0300, Marcel Apfelbaum wrote:
>
> On 07/26/2018 07:42 PM, Knut Omang wrote:
> > On Thu, 2018-07-26 at 19:41 +0300, Michael S. Tsirkin wrote:
> > > On Thu, Jul 26, 2018 at 06:38:32PM +0200, Knut Omang wrote:
> > > > On Thu, 2018-07-26 at 18:51 +0300, Marcel Apfelbaum wr
Eric Blake writes:
> On 07/26/2018 01:18 AM, Markus Armbruster wrote:
>> Signed-off-by: Markus Armbruster
>> ---
>> qobject/qstring.c | 6 +-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/qobject/qstring.c b/qobject/qstring.c
>> index 18b8eb82f8..7990569c5a 100644
>
On 07/25/2018 11:48 PM, Shivaprasad G Bhat wrote:
> Reference:
> https://refspecs.linuxfoundation.org/ELF/ppc64/PPC-elf64abi-1.9.html#REG
This document is for _CALL_ELF < 2. For ppc64le, the document is at
https://openpowerfoundation.org/wp-content/uploads/2016/03/ABI64BitOpenPOWERv1.1_16July201
On Wed, Jul 25, 2018 at 04:39:28PM +0200, Igor Mammedov wrote:
> Fixed dynamic tables are usually more or less self sufficient
> so it's safer to reload so I'm ok with their reloading.
Well it's just a matter of excercising self-control and
building sane APIs to make sure we do.
E.g. let's say we
On Thu, 26 Jul 2018 20:11:44 +0300
"Michael S. Tsirkin" wrote:
> On Thu, Jul 26, 2018 at 10:42:52AM -0600, Alex Williamson wrote:
> > On Thu, 26 Jul 2018 19:14:45 +0300
> > "Michael S. Tsirkin" wrote:
> >
> > > On Thu, Jul 26, 2018 at 06:51:13PM +0300, Marcel Apfelbaum wrote:
> > > > Hi
> >
On Thu, 2018-07-26 at 20:11 +0300, Michael S. Tsirkin wrote:
> On Thu, Jul 26, 2018 at 10:42:52AM -0600, Alex Williamson wrote:
> > On Thu, 26 Jul 2018 19:14:45 +0300
> > "Michael S. Tsirkin" wrote:
> >
> > > On Thu, Jul 26, 2018 at 06:51:13PM +0300, Marcel Apfelbaum wrote:
> > > > Hi
> > > >
>
Alex Bennée writes:
> Pavel Dovgalyuk writes:
>
>> Replay is capable of recording normal BH events, but sometimes
>> there are single use callbacks scheduled with aio_bh_schedule_oneshot
>> function. This patch enables recording and replaying such callbacks.
>> Block layer uses these events fo
On 07/26/2018 01:26 AM, David Gibson wrote:
On Tue, Dec 12, 2017 at 03:44:02PM -0500, Stefan Berger wrote:
Implement support for TPM on ppc64 by implementing the vTPM CRQ
interface as a frontend. It can use the tpm_emulator driver
backend with the external swtpm.
The Linux vTPM driver for ppc64
Pavel Dovgalyuk writes:
> Replay is capable of recording normal BH events, but sometimes
> there are single use callbacks scheduled with aio_bh_schedule_oneshot
> function. This patch enables recording and replaying such callbacks.
> Block layer uses these events for calling the completion func
On 07/25/2018 11:48 PM, Shivaprasad G Bhat wrote:
> r11 is a volatile register on PPC as per calling conventions.
> The safe_syscall code uses it to check if the signal_pending
> is set during the safe_syscall. When a syscall is interrupted
> on return from signal handling, the r11 might be corrupt
On Thu, Jul 26, 2018 at 10:42:52AM -0600, Alex Williamson wrote:
> On Thu, 26 Jul 2018 19:14:45 +0300
> "Michael S. Tsirkin" wrote:
>
> > On Thu, Jul 26, 2018 at 06:51:13PM +0300, Marcel Apfelbaum wrote:
> > > Hi
> > >
> > > On 07/26/2018 05:52 PM, Stefan Hajnoczi wrote:
> > > > On Thu, Jul 12
On 07/26/2018 07:42 PM, Knut Omang wrote:
On Thu, 2018-07-26 at 19:41 +0300, Michael S. Tsirkin wrote:
On Thu, Jul 26, 2018 at 06:38:32PM +0200, Knut Omang wrote:
On Thu, 2018-07-26 at 18:51 +0300, Marcel Apfelbaum wrote:
Hi
On 07/26/2018 05:52 PM, Stefan Hajnoczi wrote:
On Thu, Jul 12, 2
Am 26.07.2018 um 18:46 hat Nir Soffer geschrieben:
> On Thu, Jul 26, 2018 at 7:10 PM Eric Blake wrote:
>
> > On 07/26/2018 10:33 AM, Kevin Wolf wrote:
> >
> > >
> > > As far as I know, the comment you quoted is accurate for BLKDISCARD and
> > > BLKZEROOUT, but not for the fallocate() flags.
> > >
Sorry I did not have any time for this last days. And this
to make it worse this is a follow up to something that was
half a year ago. That means I have to re-familiarize myself
with the topic.
If I don't get around to answer in couple of weeks, feel
free to ping me.
Since from what I've seen mo
On Thu, Jul 26, 2018 at 7:41 PM Kevin Wolf wrote:
...
> > > +#ifdef CONFIG_FALLOCATE_PUNCH_HOLE
> > > +ret = do_fallocate(s->fd, FALLOC_FL_PUNCH_HOLE |
> FALLOC_FL_KEEP_SIZE,
> > > + aiocb->aio_offset, aiocb->aio_nbytes);
> > > +if (ret != -ENOTSUP) {
> > >
> >
> > T
On Thu, Jul 26, 2018 at 7:10 PM Eric Blake wrote:
> On 07/26/2018 10:33 AM, Kevin Wolf wrote:
>
> >
> > As far as I know, the comment you quoted is accurate for BLKDISCARD and
> > BLKZEROOUT, but not for the fallocate() flags.
> >
>
> I sure wish the man pages were more explicit on what guarantee
On Thu, 2018-07-26 at 19:41 +0300, Michael S. Tsirkin wrote:
> On Thu, Jul 26, 2018 at 06:38:32PM +0200, Knut Omang wrote:
> > On Thu, 2018-07-26 at 18:51 +0300, Marcel Apfelbaum wrote:
> > > Hi
> > >
> > > On 07/26/2018 05:52 PM, Stefan Hajnoczi wrote:
> > > > On Thu, Jul 12, 2018 at 07:33:14AM +
On Thu, 26 Jul 2018 19:14:45 +0300
"Michael S. Tsirkin" wrote:
> On Thu, Jul 26, 2018 at 06:51:13PM +0300, Marcel Apfelbaum wrote:
> > Hi
> >
> > On 07/26/2018 05:52 PM, Stefan Hajnoczi wrote:
> > > On Thu, Jul 12, 2018 at 07:33:14AM +, Elijah Shakkour wrote:
> > > > Hey,
> > > >
> > >
Am 26.07.2018 um 18:22 hat Nir Soffer geschrieben:
> On Thu, Jul 26, 2018 at 2:33 PM Kevin Wolf wrote:
>
> > The BLKDISCARD ioctl doesn't guarantee that the discarded blocks read as
> > all-zero afterwards, so don't try to abuse it for zero writing. We try
> > to only use this if BLKDISCARDZEROES
On Thu, Jul 26, 2018 at 06:38:32PM +0200, Knut Omang wrote:
> On Thu, 2018-07-26 at 18:51 +0300, Marcel Apfelbaum wrote:
> > Hi
> >
> > On 07/26/2018 05:52 PM, Stefan Hajnoczi wrote:
> > > On Thu, Jul 12, 2018 at 07:33:14AM +, Elijah Shakkour wrote:
> > > > Hey,
> > > >
> > > > Our team is ad
On Thu, 2018-07-26 at 18:51 +0300, Marcel Apfelbaum wrote:
> Hi
>
> On 07/26/2018 05:52 PM, Stefan Hajnoczi wrote:
> > On Thu, Jul 12, 2018 at 07:33:14AM +, Elijah Shakkour wrote:
> > > Hey,
> > >
> > > Our team is adding a NIC functional emulation to QEMU.
> > > One of the features we are a
On Thu, Jul 26, 2018 at 07:34:41PM +0300, Marcel Apfelbaum wrote:
>
>
> On 07/26/2018 07:14 PM, Michael S. Tsirkin wrote:
> > On Thu, Jul 26, 2018 at 06:51:13PM +0300, Marcel Apfelbaum wrote:
> > > Hi
> > >
> > > On 07/26/2018 05:52 PM, Stefan Hajnoczi wrote:
> > > > On Thu, Jul 12, 2018 at 07:3
On 07/26/2018 07:14 PM, Michael S. Tsirkin wrote:
On Thu, Jul 26, 2018 at 06:51:13PM +0300, Marcel Apfelbaum wrote:
Hi
On 07/26/2018 05:52 PM, Stefan Hajnoczi wrote:
On Thu, Jul 12, 2018 at 07:33:14AM +, Elijah Shakkour wrote:
Hey,
Our team is adding a NIC functional emulation to QEM
On Thu, Jul 26, 2018 at 2:33 PM Kevin Wolf wrote:
> The BLKDISCARD ioctl doesn't guarantee that the discarded blocks read as
> all-zero afterwards, so don't try to abuse it for zero writing. We try
> to only use this if BLKDISCARDZEROES tells us that it is safe, but this
> is unreliable on older
On Thu, Jul 26, 2018 at 06:51:13PM +0300, Marcel Apfelbaum wrote:
> Hi
>
> On 07/26/2018 05:52 PM, Stefan Hajnoczi wrote:
> > On Thu, Jul 12, 2018 at 07:33:14AM +, Elijah Shakkour wrote:
> > > Hey,
> > >
> > > Our team is adding a NIC functional emulation to QEMU.
> > > One of the features w
On 07/25/2018 01:59 PM, Dr. David Alan Gilbert wrote:
* Marcel Apfelbaum (marcel.apfelb...@gmail.com) wrote:
Hi,
On 07/25/2018 10:32 AM, Thomas Huth wrote:
On 25.07.2018 06:47, Rebecca Cran wrote:
In commit 18a398f6a39df4b08ff86ac0d38384193ca5f4cc, ./configure on
FreeBSD incorrectly detect
On 07/26/2018 10:33 AM, Kevin Wolf wrote:
As far as I know, the comment you quoted is accurate for BLKDISCARD and
BLKZEROOUT, but not for the fallocate() flags.
I sure wish the man pages were more explicit on what guarantees each
flag offers.
Hmm - that thread also mentions FALLOC_FL_NO_
On Wed, Jul 25, 2018 at 05:53:35PM +0200, Igor Mammedov wrote:
> On Wed, 25 Jul 2018 15:44:37 +0300
> "Michael S. Tsirkin" wrote:
>
> > On Wed, Jul 25, 2018 at 02:32:11PM +0200, Igor Mammedov wrote:
> > > On Tue, 10 Jul 2018 03:01:30 +0300
> > > "Michael S. Tsirkin" wrote:
> > >
> > > > Now t
Hi
On 07/26/2018 05:52 PM, Stefan Hajnoczi wrote:
On Thu, Jul 12, 2018 at 07:33:14AM +, Elijah Shakkour wrote:
Hey,
Our team is adding a NIC functional emulation to QEMU.
One of the features we are adding to this NIC is SRIOV.
Here is the error message I get when checking SRIOV support o
On Wed, Jul 25, 2018 at 04:49:08PM +0200, Igor Mammedov wrote:
> On Wed, 25 Jul 2018 15:50:09 +0300
> "Michael S. Tsirkin" wrote:
>
> > On Wed, Jul 25, 2018 at 02:37:24PM +0200, Igor Mammedov wrote:
> > > On Tue, 10 Jul 2018 03:01:34 +0300
> > > "Michael S. Tsirkin" wrote:
> > >
> > > > Based
Pavel Dovgalyuk writes:
> Replay is capable of recording normal BH events, but sometimes
> there are single use callbacks scheduled with aio_bh_schedule_oneshot
> function. This patch enables recording and replaying such callbacks.
> Block layer uses these events for calling the completion func
Am 26.07.2018 um 17:23 hat Eric Blake geschrieben:
> On 07/26/2018 10:06 AM, Kevin Wolf wrote:
>
> > > > +#ifdef CONFIG_FALLOCATE_PUNCH_HOLE
> > > > +ret = do_fallocate(s->fd, FALLOC_FL_PUNCH_HOLE |
> > > > FALLOC_FL_KEEP_SIZE,
> > > > + aiocb->aio_offset, aiocb->aio_nby
On 07/26/2018 10:06 AM, Kevin Wolf wrote:
+#ifdef CONFIG_FALLOCATE_PUNCH_HOLE
+ret = do_fallocate(s->fd, FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE,
+ aiocb->aio_offset, aiocb->aio_nbytes);
Umm, doesn't this have to use FALLOC_FL_ZERO_RANGE? FALLOC_FL_PUNCH_HOLE
deall
* Paolo Bonzini (pbonz...@redhat.com) wrote:
> On 25/07/2018 22:04, Andrea Arcangeli wrote:
> >
> > It may look like the uffd-wp model is wish-feature similar to an
> > optimization, but without the uffd-wp model when the WP fault is
> > triggered by kernel code, the sigsegv model falls apart and
On Thu, Jul 26, 2018 at 09:29:44AM +0200, David Hildenbrand wrote:
> On 25.07.2018 22:14, Eduardo Habkost wrote:
> > On Wed, Jul 25, 2018 at 07:50:21PM +0200, David Hildenbrand wrote:
> >> On 25.07.2018 19:09, Eduardo Habkost wrote:
> > [...]
> +if (local_err) {
> +g_assert(kv
Am 26.07.2018 um 16:28 hat Eric Blake geschrieben:
> On 07/26/2018 06:33 AM, Kevin Wolf wrote:
> > The BLKDISCARD ioctl doesn't guarantee that the discarded blocks read as
> > all-zero afterwards, so don't try to abuse it for zero writing. We try
> > to only use this if BLKDISCARDZEROES tells us th
On Thu, Jul 26, 2018 at 5:28 PM Eric Blake wrote:
> On 07/26/2018 06:33 AM, Kevin Wolf wrote:
> > The BLKDISCARD ioctl doesn't guarantee that the discarded blocks read as
> > all-zero afterwards, so don't try to abuse it for zero writing. We try
> > to only use this if BLKDISCARDZEROES tells us t
Thomas Huth wrote:
> On 17.07.2018 13:33, Juan Quintela wrote:
>> Signed-off-by: Juan Quintela
>> ---
>> tests/Makefile.include | 8
>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/tests/Makefile.include b/tests/Makefile.include
>> index b3e707e8c3..ccf71bddcc 100
On Thu, Jul 12, 2018 at 07:33:14AM +, Elijah Shakkour wrote:
> Hey,
>
> Our team is adding a NIC functional emulation to QEMU.
> One of the features we are adding to this NIC is SRIOV.
>
> Here is the error message I get when checking SRIOV support of our emulated
> NIC on Win2016 server (
How about:
"default: 4 times the cluster size; or if cache-size is specified, the part
of it which is not used for the L2 cache"
Even simpler, easier to understand and more accurate. I like it.
Thanks!
Kevin
On 07/26/2018 05:42 PM, Kevin Wolf wrote:
Am 26.07.2018 um 14:24 hat Leonid Bloch geschrieben:
You mean with QDict? I'll look into that now. But already sent v5 before
reading this email.
Yes, with reading it from the QDict. (Or whatever the simplest way is
that results in the right external i
Am 26.07.2018 um 16:27 hat Leonid Bloch geschrieben:
> On 07/26/2018 01:02 PM, Kevin Wolf wrote:
> > Am 25.07.2018 um 16:27 hat Leonid Bloch geschrieben:
> > > Signed-off-by: Leonid Bloch
> > > ---
> > > docs/qcow2-cache.txt | 3 +++
> > > qemu-options.hx | 10 ++
> > > 2 files c
Am 26.07.2018 um 14:24 hat Leonid Bloch geschrieben:
> > > You mean with QDict? I'll look into that now. But already sent v5 before
> > > reading this email.
> >
> > Yes, with reading it from the QDict. (Or whatever the simplest way is
> > that results in the right external interface, but I suppos
On 07/26/2018 05:20 PM, Eric Blake wrote:
On 07/26/2018 05:02 AM, Kevin Wolf wrote:
Am 25.07.2018 um 16:27 hat Leonid Bloch geschrieben:
Signed-off-by: Leonid Bloch
---
docs/qcow2-cache.txt | 3 +++
qemu-options.hx | 10 ++
2 files changed, 9 insertions(+), 4 deletions(-)
On 07/26/2018 06:33 AM, Kevin Wolf wrote:
The BLKDISCARD ioctl doesn't guarantee that the discarded blocks read as
all-zero afterwards, so don't try to abuse it for zero writing. We try
to only use this if BLKDISCARDZEROES tells us that it is safe, but this
is unreliable on older kernels and a co
1 - 100 of 174 matches
Mail list logo
