qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
	"Cédric Le Goater" <clg@kaod.org>, "Greg Kurz" <groug@kaod.org>
Subject: Re: [Qemu-devel] [PATCH v4 1/5] spapr: Implement dispatch counter and prod bit on tcg
Date: Wed, 17 Jul 2019 11:51:15 +1000	[thread overview]
Message-ID: <20190717015115.GA9123@umbus.fritz.box> (raw)
In-Reply-To: <1563269012.r4tmfz9h7z.astroid@bobo.none>

[-- Attachment #1: Type: text/plain, Size: 1862 bytes --]

On Tue, Jul 16, 2019 at 07:27:22PM +1000, Nicholas Piggin wrote:
> David Gibson's on July 16, 2019 5:34 pm:
> > On Tue, Jul 16, 2019 at 12:47:22PM +1000, Nicholas Piggin wrote:
> >> Implement cpu_exec_enter/exit on ppc which calls into new methods of
> >> the same name in PPCVirtualHypervisorClass. These are used by spapr
> >> to implement these splpar elements, used in subsequent changes.
> >> 
> >> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
> >> ---
> >>  hw/ppc/spapr.c                  | 25 +++++++++++++++++++++++++
> >>  hw/ppc/spapr_cpu_core.c         |  5 ++++-
> >>  hw/ppc/spapr_hcall.c            |  5 -----
> >>  include/hw/ppc/spapr.h          |  7 +++++++
> >>  include/hw/ppc/spapr_cpu_core.h |  2 ++
> >>  target/ppc/cpu.h                |  2 ++
> >>  target/ppc/translate_init.inc.c | 25 +++++++++++++++++++++++++
> >>  7 files changed, 65 insertions(+), 6 deletions(-)
> > 
> > Mostly LGTM.  Please do address the style issues that the bot
> > reported.
> 
> Will do.
> 
> > In addition, do the dispatch_counter and prod values need to be
> > migrated?
> 
> I was thinking no, it should be just a blip. But could the guest
> be reading the dispatch counter in the vpa for some other reason?
> There are other (unimplemented) dispatch statistics in there AFAIKS.
> Linux doesn't, but others might.

Right, I guess it's a question of whether a guest would get confused
if the dispatch count suddenly resets.

> And what about KVM, does any of the VPA data get migrated for 
> KVM guests?

Well, the stuff that's actually written into the VPA is implicitly
migrated, since it's part of guest memory.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-07-17  2:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-16  2:47 [Qemu-devel] [PATCH v4 0/5] spapr: implement dispatch and suspend calls Nicholas Piggin
2019-07-16  2:47 ` [Qemu-devel] [PATCH v4 1/5] spapr: Implement dispatch counter and prod bit on tcg Nicholas Piggin
2019-07-16  7:34   ` David Gibson
2019-07-16  9:27     ` Nicholas Piggin
2019-07-17  1:51       ` David Gibson [this message]
2019-07-17  5:51         ` Nicholas Piggin
2019-07-16  2:47 ` [Qemu-devel] [PATCH v4 2/5] spapr: Implement H_PROD Nicholas Piggin
2019-07-16  8:22   ` David Gibson
2019-07-16  2:47 ` [Qemu-devel] [PATCH v4 3/5] spapr: Implement H_CONFER Nicholas Piggin
2019-07-16  8:25   ` David Gibson
2019-07-16 10:25     ` Nicholas Piggin
2019-07-17  1:51       ` David Gibson
2019-07-16  2:47 ` [Qemu-devel] [PATCH v4 4/5] spapr: Implement H_JOIN Nicholas Piggin
2019-07-16  8:26   ` David Gibson
2019-07-16  2:47 ` [Qemu-devel] [PATCH v4 5/5] spapr: Implement ibm,suspend-me Nicholas Piggin
2019-07-16  8:30   ` David Gibson
2019-07-16 11:15     ` Nicholas Piggin
2019-07-17  1:54       ` David Gibson
2019-07-16  2:55 ` [Qemu-devel] [PATCH v4 0/5] spapr: implement dispatch and suspend calls no-reply

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=20190717015115.GA9123@umbus.fritz.box \
    --to=david@gibson.dropbear.id.au \
    --cc=clg@kaod.org \
    --cc=groug@kaod.org \
    --cc=npiggin@gmail.com \
    --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).