From: Alexander Graf <agraf@suse.de>
To: sam.mj@au1.ibm.com, qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 2/2] spapr: Fix stale HTAB during live migration (TCG)
Date: Wed, 05 Nov 2014 23:04:21 +0100 [thread overview]
Message-ID: <545A9EE5.5050600@suse.de> (raw)
In-Reply-To: <545A9E13.2000804@au1.ibm.com>
On 05.11.14 23:00, Samuel Mendoza-Jonas wrote:
> On 05/11/14 19:05, Alexander Graf wrote:
>>
>>
>> On 05.11.14 07:17, Samuel Mendoza-Jonas wrote:
>>> If a TCG guest reboots during a running migration HTAB entries are not
>>> marked dirty, and the destination boots with an invalid HTAB.
>>>
>>> When a reboot occurs reset the state of HTAB migration, and explicitly
>>> inform the destination of invalid entries.
>>>
>>> Signed-off-by: Samuel Mendoza-Jonas <sam.mj@au1.ibm.com>
>>> ---
>>> hw/ppc/spapr.c | 59 +++++++++++++++++++++++++++++++++++---------------
>>> include/hw/ppc/spapr.h | 1 +
>>> 2 files changed, 42 insertions(+), 18 deletions(-)
>>>
>>> diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c
>>> index 1610c28..9f419e8 100644
>>> --- a/hw/ppc/spapr.c
>>> +++ b/hw/ppc/spapr.c
>>> @@ -829,26 +829,30 @@ static void spapr_reset_htab(sPAPREnvironment *spapr)
>>>
>>> shift = kvmppc_reset_htab(spapr->htab_shift);
>>>
>>> + pthread_mutex_lock(&spapr->htab_mutex);
>>> if (shift > 0) {
>>> /* Kernel handles htab, we don't need to allocate one */
>>> spapr->htab_shift = shift;
>>> kvmppc_kern_htab = true;
>>>
>>> /* Tell readers to update their file descriptor */
>>> - pthread_mutex_lock(&spapr->htab_mutex);
>>> if (spapr->htab_fd > 0) {
>>> spapr->htab_fd_stale = true;
>>> }
>>> - pthread_mutex_unlock(&spapr->htab_mutex);
>>> } else {
>>> if (!spapr->htab) {
>>> /* Allocate an htab if we don't yet have one */
>>> spapr->htab = qemu_memalign(HTAB_SIZE(spapr), HTAB_SIZE(spapr));
>>> + } else {
>>> + spapr->htab_mig_full = true;
>>> + spapr->htab_first_pass = true;
>>> + spapr->htab_save_index = 0;
>>
>> You could just set the dirty bitmap to "all dirty" here, no? Then you
>> don't need all the changes belong I presume?
>
> Yes, then you just need to reset htab_save_index to zero. The idea of this approach
> was to avoid walking the HTAB twice (once to dirty and once to read it). But it is
> a lot of changes for a fairly small benefit. If setting it dirty is preferred I'll
> test and send that version. Thanks!
Yes, please. I would prefer to keep this code as simple as I can ;). And
the less corner cases we need to watch out for, the easier it becomes.
Alex
next prev parent reply other threads:[~2014-11-05 22:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 6:16 [Qemu-devel] [PATCH 0/2] spapr: Fix stale HTAB during live migration Samuel Mendoza-Jonas
2014-11-05 6:17 ` [Qemu-devel] [PATCH 1/2] spapr: Fix stale HTAB during live migration (KVM) Samuel Mendoza-Jonas
2014-11-05 7:57 ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
2014-11-05 21:56 ` Samuel Mendoza-Jonas
2014-11-13 6:59 ` [Qemu-devel] " Alexey Kardashevskiy
2014-11-05 6:17 ` [Qemu-devel] [PATCH 2/2] spapr: Fix stale HTAB during live migration (TCG) Samuel Mendoza-Jonas
2014-11-05 8:05 ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
2014-11-05 22:00 ` Samuel Mendoza-Jonas
2014-11-05 22:04 ` Alexander Graf [this message]
2014-11-13 7:12 ` [Qemu-devel] " Alexey Kardashevskiy
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=545A9EE5.5050600@suse.de \
--to=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=sam.mj@au1.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.