From: David Gibson <david@gibson.dropbear.id.au>
To: Laurent Vivier <lvivier@redhat.com>
Cc: Bharata B Rao <bharata@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, rnsastry@linux.vnet.ibm.com,
qemu-ppc@nongnu.org, sam.bobroff@au1.ibm.com
Subject: Re: [Qemu-devel] [RFC PATCH v2 3/4] spapr: Make h_register_process_table hcall flags global
Date: Mon, 22 May 2017 12:41:18 +1000 [thread overview]
Message-ID: <20170522024118.GK30246@umbus.fritz.box> (raw)
In-Reply-To: <13948266-7fd2-a752-3546-cb236f87d16d@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2237 bytes --]
On Sun, May 21, 2017 at 08:48:42PM +0200, Laurent Vivier wrote:
> On 19/05/2017 07:40, Bharata B Rao wrote:
> > The flags used in h_register_process_table hcall are needed in spapr.c
> > and hence move them to a header file. While doing so, give them
> > slightly specific names.
> >
> > Signed-off-by: Bharata B Rao <bharata@linux.vnet.ibm.com>
> > Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
> > ---
> > hw/ppc/spapr_hcall.c | 31 ++++++++++++++-----------------
> > include/hw/ppc/spapr.h | 10 ++++++++++
> > 2 files changed, 24 insertions(+), 17 deletions(-)
> >
> > diff --git a/hw/ppc/spapr_hcall.c b/hw/ppc/spapr_hcall.c
> > index cea5d99..3915e6f 100644
> > --- a/hw/ppc/spapr_hcall.c
> > +++ b/hw/ppc/spapr_hcall.c
> > @@ -921,13 +921,6 @@ static void spapr_check_setup_free_hpt(sPAPRMachineState *spapr,
> > return;
> > }
> >
> > -#define FLAGS_MASK 0x01FULL
> > -#define FLAG_MODIFY 0x10
> > -#define FLAG_REGISTER 0x08
> > -#define FLAG_RADIX 0x04
> > -#define FLAG_HASH_PROC_TBL 0x02
> > -#define FLAG_GTSE 0x01
> > -
> ...
> > diff --git a/include/hw/ppc/spapr.h b/include/hw/ppc/spapr.h
> > index e581c4a..588872a 100644
> > --- a/include/hw/ppc/spapr.h
> > +++ b/include/hw/ppc/spapr.h
> > @@ -685,4 +685,14 @@ int spapr_rng_populate_dt(void *fdt);
> >
> > void spapr_do_system_reset_on_cpu(CPUState *cs, run_on_cpu_data arg);
> >
> > +/*
> > + * Defines for flag value used in H_REGISTER_PROC_TBL hcall.
> > + */
> > +#define SPAPR_PROC_TABLE_MASK 0x01FULL
> > +#define SPAPR_PROC_TABLE_MODIFY 0x10
> > +#define SPAPR_PROC_TABLE_REGISTER 0x08
> > +#define SPAPR_PROC_TABLE_RADIX 0x04
> > +#define SPAPR_PROC_TABLE_HPT_PT 0x02
> > +#define SPAPR_PROC_TABLE_GTSE 0x01
>
> I think it should be cleaner if you use 0x1fULL
I agree, but looking at the new version of the final patch, I don't
think this patch will actually be necessary any more.
--
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: 819 bytes --]
next prev parent reply other threads:[~2017-05-22 3:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 5:40 [Qemu-devel] [RFC PATCH v2 0/4] ppc/spapr: Fix migration of radix guests Bharata B Rao
2017-05-19 5:40 ` [Qemu-devel] [RFC PATCH v2 1/4] migration: Introduce unregister_savevm_live() Bharata B Rao
2017-05-19 7:33 ` David Gibson
2017-05-19 13:14 ` Laurent Vivier
2017-05-22 2:36 ` David Gibson
2017-05-19 5:40 ` [Qemu-devel] [RFC PATCH v2 2/4] spapr: Unregister HPT savevm handlers for radix guests Bharata B Rao
2017-05-22 2:35 ` David Gibson
2017-05-19 5:40 ` [Qemu-devel] [RFC PATCH v2 3/4] spapr: Make h_register_process_table hcall flags global Bharata B Rao
2017-05-21 18:48 ` Laurent Vivier
2017-05-22 2:41 ` David Gibson [this message]
2017-05-19 5:40 ` [Qemu-devel] [RFC PATCH v2 4/4] spapr: Fix migration of Radix guests Bharata B Rao
2017-05-19 6:36 ` Bharata B Rao
2017-05-22 2:44 ` David Gibson
2017-05-22 4:15 ` Bharata B Rao
2017-05-22 6:30 ` [Qemu-devel] [Qemu-ppc] " Suraj Jitindar Singh
2017-05-23 4:48 ` Bharata B Rao
2017-05-23 8:42 ` Suraj Jitindar Singh
2017-05-23 9:00 ` Bharata B Rao
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=20170522024118.GK30246@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=bharata@linux.vnet.ibm.com \
--cc=lvivier@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=rnsastry@linux.vnet.ibm.com \
--cc=sam.bobroff@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 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).