[Qemu-devel] [PATCH v6 29/29] postcopy shared docs

From: "Dr. David Alan Gilbert" Add some notes to the migration documentation for shared memory postcopy. Signed-off-by: Dr. David Alan Gilbert Reviewed-by: Marc-André Lureau --- docs/devel/migration.rst | 41

Re: [Qemu-devel] Deprecate tilegx ?

> Le 14/03/2018 �� 10:09, Xuetao Guan a 茅crit��: >> >>> [...] >>> Personally, I think it's useful to consider not merely "do we >>> have anybody actively maintaining this" (after all our x86 frontend >>> is not exactly very well-loved!) but also "are there users of QEMU >>> out there using it?"

[Qemu-devel] [PATCH v6 19/29] postcopy: helper for waking shared

From: "Dr. David Alan Gilbert" Provide a helper to send a 'wake' request on a userfaultfd for a shared process. The address in the clients address space is specified together with the RAMBlock it was resolved to. Signed-off-by: Dr. David Alan Gilbert

[Qemu-devel] [PATCH v6 22/29] vhost+postcopy: Call wakeups

From: "Dr. David Alan Gilbert" Cause the vhost-user client to be woken up whenever: a) We place a page in postcopy mode b) We get a fault and the page has already been received Signed-off-by: Dr. David Alan Gilbert --- migration/postcopy-ram.c |

[Qemu-devel] [PATCH v6 17/29] vhost+postcopy: Helper to send requests to source for shared pages

From: "Dr. David Alan Gilbert" Provide a helper to be used by shared waker functions to request shared pages from the source. The last_rb pointer is moved into the incoming state since this helper can update it as well as the main fault thread function. Signed-off-by: Dr.

[Qemu-devel] [PATCH v6 21/29] vhost+postcopy: Add vhost waker

From: "Dr. David Alan Gilbert" Register a waker function in vhost-user code to be notified when pages arrive or requests to previously mapped pages get requested. Signed-off-by: Dr. David Alan Gilbert Reviewed-by: Marc-André Lureau

[Qemu-devel] [PATCH v6 27/29] postcopy: Allow shared memory

From: "Dr. David Alan Gilbert" Now that we have the mechanisms in here, allow shared memory in a postcopy. Note that QEMU can't tell who all the users of shared regions are and thus can't tell whether all the users of the shared regions have appropriate support for

[Qemu-devel] [PATCH v6 25/29] vhost+postcopy: Wire up POSTCOPY_END notify

From: "Dr. David Alan Gilbert" Wire up a call to VHOST_USER_POSTCOPY_END message to the vhost clients right before we ask the listener thread to shutdown. Signed-off-by: Dr. David Alan Gilbert Reviewed-by: Marc-André Lureau

[Qemu-devel] [PATCH v6 14/29] libvhost-user+postcopy: Register new regions with the ufd

From: "Dr. David Alan Gilbert" When new regions are sent to the client using SET_MEM_TABLE, register them with the userfaultfd. Signed-off-by: Dr. David Alan Gilbert Reviewed-by: Marc-André Lureau ---

[Qemu-devel] [PATCH v6 20/29] postcopy: postcopy_notify_shared_wake

From: "Dr. David Alan Gilbert" Add a hook to allow a client userfaultfd to be 'woken' when a page arrives, and a walker that calls that hook for relevant clients given a RAMBlock and offset. Signed-off-by: Dr. David Alan Gilbert Reviewed-by: Peter Xu

[Qemu-devel] [PATCH v6 16/29] vhost+postcopy: Stash RAMBlock and offset

From: "Dr. David Alan Gilbert" Stash the RAMBlock and offset for later use looking up addresses. Signed-off-by: Dr. David Alan Gilbert --- hw/virtio/trace-events | 1 + hw/virtio/vhost-user.c | 49 + 2

[Qemu-devel] [PATCH v6 11/29] vhost+postcopy: Transmit 'listen' to slave

From: "Dr. David Alan Gilbert" Notify the vhost-user slave on reception of the 'postcopy-listen' event from the source. Signed-off-by: Dr. David Alan Gilbert Reviewed-by: Marc-André Lureau Reviewed-by: Peter Xu

[Qemu-devel] [PATCH v6 13/29] migration/ram: ramblock_recv_bitmap_test_byte_offset

From: "Dr. David Alan Gilbert" Utility for testing the map when you already know the offset in the RAMBlock. Signed-off-by: Dr. David Alan Gilbert Reviewed-by: Peter Xu Reviewed-by: Marc-André Lureau

[Qemu-devel] [PATCH v6 18/29] vhost+postcopy: Resolve client address

From: "Dr. David Alan Gilbert" Resolve fault addresses read off the clients UFD into RAMBlock and offset, and call back to the postcopy code to ask for the page. Signed-off-by: Dr. David Alan Gilbert Reviewed-by: Peter Xu

[Qemu-devel] [PATCH v6 09/29] postcopy: Allow registering of fd handler

From: "Dr. David Alan Gilbert" Allow other userfaultfd's to be registered into the fault thread so that handlers for shared memory can get responses. Signed-off-by: Dr. David Alan Gilbert Reviewed-by: Peter Xu ---

[Qemu-devel] [PATCH v6 10/29] vhost+postcopy: Register shared ufd with postcopy

From: "Dr. David Alan Gilbert" Register the UFD that comes in as the response to the 'advise' method with the postcopy code. Signed-off-by: Dr. David Alan Gilbert Reviewed-by: Marc-André Lureau --- hw/virtio/vhost-user.c

[Qemu-devel] [PATCH v6 07/29] libvhost-user: Support sending fds back to qemu

From: "Dr. David Alan Gilbert" Allow replies with fds (for postcopy) Signed-off-by: Dr. David Alan Gilbert Reviewed-by: Marc-André Lureau --- contrib/libvhost-user/libvhost-user.c | 30 +- 1

[Qemu-devel] [PATCH v6 06/29] vhost-user: Add 'VHOST_USER_POSTCOPY_ADVISE' message

From: "Dr. David Alan Gilbert" Wire up a notifier to send a VHOST_USER_POSTCOPY_ADVISE message on an incoming advise. Later patches will fill in the behaviour/contents of the message. Signed-off-by: Dr. David Alan Gilbert Reviewed-by: Marc-André

[Qemu-devel] [PATCH v6 15/29] vhost+postcopy: Send address back to qemu

From: "Dr. David Alan Gilbert" We need a better way, but at the moment we need the address of the mappings sent back to qemu so it can interpret the messages on the userfaultfd it reads. This is done as a 3 stage set: QEMU -> client set_mem_table mmap stuff,

[Qemu-devel] [PATCH v6 00/29] postcopy+vhost-user/shared ram

From: "Dr. David Alan Gilbert" This set enables postcopy migration with shared memory to a vhost user process. It's based off current head. Testing is mostly performed with dpdk, with corresponding modifications by Maxime. v6 is a rebase on top of Michael's PCI

[Qemu-devel] [PATCH v6 12/29] postcopy+vhost-user: Split set_mem_table for postcopy

From: "Dr. David Alan Gilbert" Split the set_mem_table routines in both qemu and libvhost-user because the postcopy versions are going to be quite different once changes in the later patches are added. However, this patch doesn't produce any functional change, just the

[Qemu-devel] [PATCH v6 08/29] libvhost-user: Open userfaultfd

From: "Dr. David Alan Gilbert" Open a userfaultfd (on a postcopy_advise) and send it back in the reply to the qemu for it to monitor. Signed-off-by: Dr. David Alan Gilbert Reviewed-by: Marc-André Lureau ---

[Qemu-devel] [PATCH v6 03/29] postcopy: use UFFDIO_ZEROPAGE only when available

From: "Dr. David Alan Gilbert" Use a flag on the RAMBlock to state whether it has the UFFDIO_ZEROPAGE capability, use it when it's available. This allows the use of postcopy on tmpfs as well as hugepage backed files. Signed-off-by: Dr. David Alan Gilbert

[Qemu-devel] [PATCH v6 02/29] qemu_ram_block_host_offset

From: "Dr. David Alan Gilbert" Utility to give the offset of a host pointer within a RAMBlock (assuming we already know it's in that RAMBlock) Signed-off-by: Dr. David Alan Gilbert Reviewed-by: Peter Xu --- exec.c

[Qemu-devel] [PATCH v6 05/29] postcopy: Add vhost-user flag for postcopy and check it

From: "Dr. David Alan Gilbert" Add a vhost feature flag for postcopy support, and use the postcopy notifier to check it before allowing postcopy. Signed-off-by: Dr. David Alan Gilbert Reviewed-by: Peter Xu ---

[Qemu-devel] [PATCH v6 01/29] migrate: Update ram_block_discard_range for shared

From: "Dr. David Alan Gilbert" The choice of call to discard a block is getting more complicated for other cases. We use fallocate PUNCH_HOLE in any file cases; it works for both hugepage and for tmpfs. We use the DONTNEED for non-hugepage cases either where they're

[Qemu-devel] [PATCH v6 04/29] postcopy: Add notifier chain

From: "Dr. David Alan Gilbert" Add a notifier chain for postcopy with a 'reason' flag and an opportunity for a notifier member to return an error. Call it when enabling postcopy. This will initially used to enable devices to declare they're unable to postcopy and later to

Re: [Qemu-devel] [PULL 00/69] Misc patches for QEMU soft freeze

On 14/03/2018 12:30, Eric Blake wrote: > On 03/14/2018 05:12 AM, Paolo Bonzini wrote: > Checking PATCH 16/69: chardev: tcp: postpone async connection setup... Checking PATCH 17/69: chardev: tcp: let TLS run on chardev context... >>> >>> It seems that Dan's last patch is still missing in

Re: [Qemu-devel] [PATCH v5 00/29] postcopy+vhost-user/shared ram

* Michael S. Tsirkin (m...@redhat.com) wrote: > On Mon, Mar 12, 2018 at 05:20:55PM +, Dr. David Alan Gilbert (git) wrote: > > From: "Dr. David Alan Gilbert" > > > > This set enables postcopy migration with shared memory to a vhost user > > process. > > It's based off

Re: [Qemu-devel] [PULL 00/69] Misc patches for QEMU soft freeze

On Wed, Mar 14, 2018 at 06:30:33AM -0500, Eric Blake wrote: > On 03/14/2018 05:12 AM, Paolo Bonzini wrote: > > > > > Checking PATCH 16/69: chardev: tcp: postpone async connection setup... > > > > Checking PATCH 17/69: chardev: tcp: let TLS run on chardev context... > > > > > > It seems that

Re: [Qemu-devel] [PULL 00/69] Misc patches for QEMU soft freeze

On 03/14/2018 05:12 AM, Paolo Bonzini wrote: Checking PATCH 16/69: chardev: tcp: postpone async connection setup... Checking PATCH 17/69: chardev: tcp: let TLS run on chardev context... It seems that Dan's last patch is still missing in the pull request:

Re: [Qemu-devel] [RFC PATCH 13/30] pc/xen: Xen Q35 support: provide IRQ handling for PCI devices

On Wed, 14 Mar 2018 11:48:46 +0100 Paolo Bonzini wrote: >On 12/03/2018 19:33, Alexey Gerasimenko wrote: >> xen_pci_slot_get_pirq --> xen_cmn_pci_slot_get_pirq >> xen_piix3_set_irq --> xen_cmn_set_irq > >Don't abbrvt names, xen_hvm_ is a better prefix. Agree, will

Re: [Qemu-devel] [PATCH 3/7] qcow: Support .bdrv_co_create

On Wed, Mar 14, 2018 at 06:16:18AM -0500, Eric Blake wrote: > On 03/09/2018 03:46 PM, Kevin Wolf wrote: > > This adds the .bdrv_co_create driver callback to qcow, which > > enables image creation over QMP. > > > > Signed-off-by: Kevin Wolf > > --- > > qapi/block-core.json |

Re: [Qemu-devel] [PATCH 3/7] qcow: Support .bdrv_co_create

On 03/09/2018 03:46 PM, Kevin Wolf wrote: This adds the .bdrv_co_create driver callback to qcow, which enables image creation over QMP. Signed-off-by: Kevin Wolf --- qapi/block-core.json | 21 +- block/qcow.c | 196

Re: [Qemu-devel] [RFC PATCH 13/30] pc/xen: Xen Q35 support: provide IRQ handling for PCI devices

On 12/03/2018 19:33, Alexey Gerasimenko wrote: > xen_pci_slot_get_pirq --> xen_cmn_pci_slot_get_pirq > xen_piix3_set_irq --> xen_cmn_set_irq Don't abbrvt names, xen_hvm_ is a better prefix. > > +fprintf(stderr, "WARNING: guest domain attempted to use > PIRQ%c " > +

Re: [Qemu-devel] regression in timer code?

On Wed, Mar 14, 2018 at 2:53 AM, Pavel Dovgalyuk wrote: > icount is adjusted by icount_warp_rt when CPU sleeps. > These adjustments may be different in different runs. > And the first adjustment is performed at the start of the machine. > Therefore "now" value includes

Re: [Qemu-devel] [PULL 0/7] Machine queue, 2018-03-12

On Tue, 13 Mar 2018 18:29:10 + Peter Maydell wrote: > On 12 March 2018 at 22:34, Eduardo Habkost wrote: > > The following changes since commit 6ceb1b51f05f9e1892d082960ed602dca7b6696e: > > > > Merge remote-tracking branch > >

Re: [Qemu-devel] [PULL 00/69] Misc patches for QEMU soft freeze

On 14/03/2018 04:35, Peter Xu wrote: > On Tue, Mar 13, 2018 at 05:15:41PM -0700, no-re...@patchew.org wrote: > > [...] > >> Your patch has style problems, please review. If any of these errors >> are false positives report them to the maintainer, see >> CHECKPATCH in MAINTAINERS. >> Checking

Re: [Qemu-devel] Deprecate tilegx ?

Le 14/03/2018 à 10:09, Xuetao Guan a écrit : > >> [...] >> Personally, I think it's useful to consider not merely "do we >> have anybody actively maintaining this" (after all our x86 frontend >> is not exactly very well-loved!) but also "are there users of QEMU >> out there using it?" and "is

Re: [Qemu-devel] [PATCH v5 09/29] postcopy: Allow registering of fd handler

* Michael S. Tsirkin (m...@redhat.com) wrote: > On Mon, Mar 12, 2018 at 05:21:04PM +, Dr. David Alan Gilbert (git) wrote: > > From: "Dr. David Alan Gilbert" > > > > Allow other userfaultfd's to be registered into the fault thread > > so that handlers for shared memory

Re: [Qemu-devel] regression in timer code?

> -Original Message- > From: Max Filippov [mailto:jcmvb...@gmail.com] > Sent: Wednesday, March 14, 2018 12:41 PM > To: Pavel Dovgalyuk > Cc: Pavel Dovgaluk; qemu-devel > Subject: Re: regression in timer code? > > On Wed, Mar 14, 2018 at 2:07 AM, Pavel Dovgalyuk

Re: [Qemu-devel] regression in timer code?

On Wed, Mar 14, 2018 at 2:07 AM, Pavel Dovgalyuk wrote: >> From: Max Filippov [mailto:jcmvb...@gmail.com] >> the commit b39e3f34c9de7ead6a11a74aa2de78baf41d81a7 >> ("icount: fixed saving/restoring of icount warp timers") has changed >> something that made timers test for

Re: [Qemu-devel] [PULL 00/13] Bitmaps patches

Hi, This series seems to have some coding style problems. See output below for more information: Type: series Message-id: 20180313211441.5179-1-js...@redhat.com Subject: [Qemu-devel] [PULL 00/13] Bitmaps patches === TEST SCRIPT BEGIN === #!/bin/bash BASE=base n=1 total=$(git log --oneline

Re: [Qemu-devel] [PATCH v11 00/13] Dirty bitmaps postcopy migration

* Su Hang (suhan...@mails.ucas.ac.cn) wrote: > > Sincerely sorry for my negligence to cause this bug! > I will fix it as quick as I can! > > Sorry again, I'm really ashamed about the mistake I have made. No need to be ashamed; bugs happen! Dave > Su Hang > > > -Original Messages- > >

[Qemu-devel] [PATCH] i386: Disable Intel PT if packets IP payloads have LIP values

Intel processor trace should be disabled when CPUID.(EAX=14H,ECX=0H).ECX.[bit31] is set. Generated packets which contain IP payloads will have LIP values when this bit is set, or IP payloads will have RIP values. Currently, The information of CPUID 14H is constant to make live migration safty and

Re: [Qemu-devel] Deprecate tilegx ?

> [...] > Personally, I think it's useful to consider not merely "do we > have anybody actively maintaining this" (after all our x86 frontend > is not exactly very well-loved!) but also "are there users of QEMU > out there using it?" and "is this actually something that exists > in the real world

Re: [Qemu-devel] regression in timer code?

> From: Max Filippov [mailto:jcmvb...@gmail.com] > the commit b39e3f34c9de7ead6a11a74aa2de78baf41d81a7 > ("icount: fixed saving/restoring of icount warp timers") has changed > something that made timers test for target/xtensa unstable. > Specifically ccount_write case in the

Re: [Qemu-devel] [PATCH V3 3/4] vfio: Add struct vfio_vmstate_info to introduce put/get callback funtion for vfio device status save/restore

> -Original Message- > From: Dr. David Alan Gilbert [mailto:dgilb...@redhat.com] > Sent: Friday, March 9, 2018 7:59 PM > To: Zhang, Yulei > Cc: qemu-devel@nongnu.org; Tian, Kevin ; > alex.william...@redhat.com; kwankh...@nvidia.com; >

[Qemu-devel] [PATCH v2 1/2] qcow2: Give the refcount cache the minimum possible size by default

The L2 and refcount caches have default sizes that can be overridden using the l2-cache-size and refcount-cache-size (an additional parameter named cache-size sets the combined size of both caches). Unless forced by one of the aforementioned parameters, QEMU will set the unspecified sizes so that

[Qemu-devel] [PATCH v2 2/2] docs: Document the new default sizes of the qcow2 caches

We have just reduced the refcount cache size to the minimum unless the user explicitly requests a larger one, so we have to update the documentation to reflect this change. Signed-off-by: Alberto Garcia Reviewed-by: Eric Blake --- docs/qcow2-cache.txt | 31

[Qemu-devel] [PATCH v2 0/2] Give the refcount cache the minimum possible size by default

Hi, we talked about this the other day, so here are the patches to change the default cache sizes in qcow2. Without this patch: * refcount-cache-size = l2-cache-size / 4 unless otherwise specified by the user. This is wasteful, the refcount cache is accessed sequentially during normal I/O, so

[Qemu-devel] [PATCH] gtk: drop pointless code from gd_window_close

Unregistering the display change listener looks like a pointless excercise given we'll exit in a moment. When exiting qemu via menu/file/quit this will not happen either. Just drop the code. Also return TRUE unconditionally. This will tell gtk to ignore the close request, so gtk will not start

Re: [Qemu-devel] [RfC PATCH] Add udmabuf misc device

Hi, > Either mlock account (because it's mlocked defacto), and get_user_pages > won't do that for you. > > Or you write the full-blown userptr implementation, including mmu_notifier > support (see i915 or amdgpu), but that also requires Christian Königs > latest ->invalidate_mapping RFC for

Re: [Qemu-devel] [PATCH v4 4/4] migration: use the free page hint feature from balloon

On 03/14/2018 10:51 AM, Michael S. Tsirkin wrote: On Wed, Mar 14, 2018 at 10:41:36AM +0800, Wei Wang wrote: On 03/14/2018 12:35 AM, Michael S. Tsirkin wrote: On Wed, Mar 07, 2018 at 08:34:25PM +0800, Wei Wang wrote: Start the free page optimization after the migration bitmap is synchronized.

Re: [Qemu-devel] [PATCH 00/19] uninorth fixes/mac_newworld board wiring improvements

On Tue, Mar 06, 2018 at 08:30:44PM +, Mark Cave-Ayland wrote: > [This is for New World Machines: there is a follow-up patch for Old World > Machines] > > This patchset is a combination of uninorth fixes/cleanup with the final aim > of removing the remaining custom init functions and

Re: [Qemu-devel] [PATCH] tests/boot-serial: Test the sam460ex board

On Wed, Mar 14, 2018 at 05:28:55AM +0100, Thomas Huth wrote: > We've got a U-Boot firmware for this board in our repository, and > the firmware prints some output to the serial console, so we can > check this board in the boot-serial tester, too. > > Signed-off-by: Thomas Huth

Re: [Qemu-devel] [PATCH 06/19] uninorth: alter pci_pmac_init() and pci_pmac_u3_init() to return uninorth device

On Tue, Mar 06, 2018 at 08:30:50PM +, Mark Cave-Ayland wrote: > This is in preparation for moving the device wiring into the New World > machine. > > Signed-off-by: Mark Cave-Ayland Applied to ppc-for-2.13. > --- > hw/pci-host/uninorth.c | 16

Re: [Qemu-devel] [PATCH 05/19] uninorth: move uninorth definitions into uninorth.h

On Tue, Mar 06, 2018 at 08:30:49PM +, Mark Cave-Ayland wrote: > Signed-off-by: Mark Cave-Ayland Applied to ppc-for-2.13. > --- > hw/pci-host/uninorth.c | 22 +-- > include/hw/pci-host/uninorth.h | 49 >

Re: [Qemu-devel] [PATCH 00/19] uninorth fixes/mac_newworld board wiring improvements

On Tue, Mar 06, 2018 at 08:30:44PM +, Mark Cave-Ayland wrote: > [This is for New World Machines: there is a follow-up patch for Old World > Machines] > > This patchset is a combination of uninorth fixes/cleanup with the final aim > of removing the remaining custom init functions and

Re: [Qemu-devel] [PATCH 08/19] uninorth: introduce temporary pic_irqs device property

On Tue, Mar 06, 2018 at 08:30:52PM +, Mark Cave-Ayland wrote: > This is in preparation for moving the PCI bus wiring inside the uninorth > host bridge devices. In the future it will be possible to remove this once the > PICs have been switched to use qdev GPIOs. > > Signed-off-by: Mark

Re: [Qemu-devel] [virtio-dev] Re: [PATCH v4 3/4] virtio-balloon: VIRTIO_BALLOON_F_FREE_PAGE_HINT

On 03/14/2018 10:53 AM, Michael S. Tsirkin wrote: On Wed, Mar 14, 2018 at 10:43:01AM +0800, Wei Wang wrote: On 03/14/2018 12:49 AM, Michael S. Tsirkin wrote: On Wed, Mar 07, 2018 at 08:34:24PM +0800, Wei Wang wrote: Signed-off-by: Wei Wang Signed-off-by: Liang Li

<    1   2