qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Simon Guo <wei.guo.simon@gmail.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
	Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH] PowerPC: Add TM bits into msr_mask
Date: Mon, 5 Mar 2018 19:02:18 +0800	[thread overview]
Message-ID: <20180305110056.GA2466@simonLocalRHEL7.x64> (raw)
In-Reply-To: <20180305062233.GL2650@umbus.fritz.box>

Hi David,
On Mon, Mar 05, 2018 at 05:22:33PM +1100, David Gibson wrote:
> On Wed, Feb 28, 2018 at 09:51:37AM +0800, wei.guo.simon@gmail.com wrote:
> > From: Simon Guo <wei.guo.simon@gmail.com>
> > 
> > During migration, cpu_post_load() will use msr_mask to determine which
> > PPC MSR bits will be sync to the target side. Hardware Transaction
> > Memory(HTM) has been supported since Power8. This patch adds TM/TS bits
> > into msr_mask for Power8, so that transactional application can be
> > migrated across qemu.
> > 
> > Signed-off-by: Simon Guo <wei.guo.simon@gmail.com>
> 
> Sorry I've taken a while to respond to this.
> 
> This addresses a real bug, but doesn't get the details quite right.
> 
> First, the MSR_TM bit is *already* included in the msr_mask for POWER8
> (it's a little above the context for this patch), though TS0 and TS1
> were not.
> 
> Second, all MSR bits are sent to the far side, it's just that without
> them in the MSR mask they'll be dropped instead of re-inserted into
> KVM.  That's the only reason the msr_mask is relevant to KVM (and TCG
> doesn't support HTM anyway).  The commit message needs to make that clearer.
> 

Thanks for the comments. I have sent v2 to correct the above.

Regards,
- Simon

      reply	other threads:[~2018-03-05 11:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-28  1:51 [Qemu-devel] [PATCH] PowerPC: Add TM bits into msr_mask wei.guo.simon
2018-03-05  6:22 ` David Gibson
2018-03-05 11:02   ` Simon Guo [this message]

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=20180305110056.GA2466@simonLocalRHEL7.x64 \
    --to=wei.guo.simon@gmail.com \
    --cc=agraf@suse.de \
    --cc=david@gibson.dropbear.id.au \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    /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).