From: David Hildenbrand <david@redhat.com>
To: "Li, Liang Z" <liang.z.li@intel.com>,
Jitendra Kolhe <jitendra.kolhe@hpe.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "crosthwaite.peter@gmail.com" <crosthwaite.peter@gmail.com>,
"ehabkost@redhat.com" <ehabkost@redhat.com>,
"quintela@redhat.com" <quintela@redhat.com>,
"simhan@hpe.com" <simhan@hpe.com>,
"JBottomley@Odin.com" <JBottomley@Odin.com>,
"armbru@redhat.com" <armbru@redhat.com>,
"lcapitulino@redhat.com" <lcapitulino@redhat.com>,
"renganathan.meenakshisundaram@hpe.com"
<renganathan.meenakshisundaram@hpe.com>,
"borntraeger@de.ibm.com" <borntraeger@de.ibm.com>,
"mst@redhat.com" <mst@redhat.com>,
"mohan_parthasarathy@hpe.com" <mohan_parthasarathy@hpe.com>,
"stefanha@redhat.com" <stefanha@redhat.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"amit.shah@redhat.com" <amit.shah@redhat.com>,
"den@openvz.org" <den@openvz.org>,
"dgilbert@redhat.com" <dgilbert@redhat.com>,
"rth@twiddle.net" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v3 0/4] migration: skip scanning and migrating ram pages released by virtio-balloon driver.
Date: Thu, 5 Jan 2017 10:41:02 +0100 [thread overview]
Message-ID: <a21b2517-08ec-653a-2e1e-9b8c325d3267@redhat.com> (raw)
In-Reply-To: <F2CBF3009FA73547804AE4C663CAB28E3C34BC76@shsmsx102.ccr.corp.intel.com>
>>
>> If we want to actually host enforce (disallow) access to inflated pages, having
>
> Is that a new feature?
Still in the design phase. Andrea Arcangeli briefly mentioned in in his
reply to v5 of your patch series
"We also plan to use userfaultfd to make the balloon driver host
enforced (will work fine on hugetlbfs 2M and tmpfs too) but that's
going to be invisible to the ABI so it's not strictly relevant for
this discussion."
>
>> such a bitmap in QEMU is required. Getting them from the guest doesn't
>> make sense in that context anymore.
>
> Even a bitmap is required, we should avoid to send it in the stop & copy stage.
yes, I agree.
Thanks!
>
> Thanks!
> Liang
>>
>> Thanks,
>> David
>>
--
David
next prev parent reply other threads:[~2017-01-05 9:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 11:20 [Qemu-devel] [PATCH v3 0/4] migration: skip scanning and migrating ram pages released by virtio-balloon driver Jitendra Kolhe
2016-05-30 10:49 ` Jitendra Kolhe
2016-06-15 6:15 ` Jitendra Kolhe
2016-12-23 2:50 ` Li, Liang Z
2016-12-26 11:47 ` Jitendra Kolhe
2017-01-02 8:54 ` David Hildenbrand
2017-01-05 1:33 ` Li, Liang Z
2017-01-05 7:04 ` Jitendra Kolhe
2017-01-05 9:41 ` David Hildenbrand [this message]
2017-01-05 10:15 ` Li, Liang Z
2017-01-05 13:47 ` David Hildenbrand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a21b2517-08ec-653a-2e1e-9b8c325d3267@redhat.com \
--to=david@redhat.com \
--cc=JBottomley@Odin.com \
--cc=amit.shah@redhat.com \
--cc=armbru@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=crosthwaite.peter@gmail.com \
--cc=den@openvz.org \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jitendra.kolhe@hpe.com \
--cc=lcapitulino@redhat.com \
--cc=liang.z.li@intel.com \
--cc=mohan_parthasarathy@hpe.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=renganathan.meenakshisundaram@hpe.com \
--cc=rth@twiddle.net \
--cc=simhan@hpe.com \
--cc=stefanha@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).