All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miles Glenn <milesg@linux.ibm.com>
To: Chinmay Rath <rathc@linux.ibm.com>,
	Shivang Upadhyay <shivangu@linux.ibm.com>,
	qemu-devel@nongnu.org, qemu-ppc@nongnu.org, npiggin@gmail.com,
	harshpb@linux.ibm.com, tommusta@gmail.com
Cc: richard.henderson@linaro.org
Subject: Re: [PATCH 6/7] target/ppc: Reorder PPC2 flags
Date: Mon, 17 Aug 2026 10:44:13 -0500	[thread overview]
Message-ID: <e4f97605390ec0829c0ae757d6e7edabf701b78e.camel@linux.ibm.com> (raw)
In-Reply-To: <728087c8-b350-4993-a64a-45aba38a616f@linux.ibm.com>

I don't have a strong opinion on this either way, but I don't think we
need a decision on this before allowing this patch set to proceed
either.  Therefore...

Reviewed-by: Glenn Miles <milesg@linux.ibm.com>

Thanks,

Glenn

On Mon, 2026-07-20 at 18:35 +0530, Chinmay Rath wrote:
> On 7/15/26 20:11, Shivang Upadhyay wrote:
> > On Wed, 2026-07-15 at 18:26 +0530, Chinmay Rath wrote:
> > > +    PPC2_BCDA_ISA206   = 0x0000000000040000ULL,
> > >       /* PPE42
> > > instructions                                                    */
> > > -    PPC2_PPE42         = 0x0000000000800000ULL,
> > > +    PPC2_PPE42         = 0x0000000000080000ULL,
> > >       /* PPE42X
> > > instructions                                                   */
> > > -    PPC2_PPE42X        = 0x0000000001000000ULL,
> > > +    PPC2_PPE42X        = 0x0000000000100000ULL,
> > >       /* PPE42XM
> > > instructions                                                  */
> > > -    PPC2_PPE42XM       = 0x0000000002000000ULL,
> > > +    PPC2_PPE42XM       = 0x0000000000200000ULL,
> > >   
> > Hi Chinmay,
> > 
> >   Would it be fine if we can do something like this instead?
> > 
> > PPC2_PPE42XM  = (1ull << 21);
> > 
> > It would be easy to see where the gaps are from next time.
> Hi Shivang,
> Thanks for the suggestion. I agree with you. Looking at the shift 
> numbers and making sure they are in consecutive incremental order would 
> make gaps less likely. However if we are to switch to this way, there 
> are about 40 such flags in cpu.h which will have to be reset in this 
> fashion. Hence should be a different patch in itself as the objective of 
> this series is different. Plus it would also bring in the risk of 
> someone shifting a bit by a value that might cause an overflow. So one 
> would have to take care of that while adding a new flag. So this way or 
> the original way, one does need to take care of couple things while 
> adding future flags.
> 
> Regards,
> Chinmay
> 
> > ~Shivang.
> > 



  reply	other threads:[~2026-08-17 15:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-15 12:56 [PATCH 0/7] target/ppc: PPC ISA 2.07 flag cleanup and updates Chinmay Rath
2026-07-15 12:56 ` [PATCH 1/7] target/ppc: Replace PPC2_VSX207 flag with PPC2_ISA207 Chinmay Rath
2026-08-14 10:49   ` Chinmay Rath
2026-08-14 10:49   ` Chinmay Rath
2026-08-17 15:17     ` Miles Glenn
2026-07-15 12:56 ` [PATCH 2/7] target/ppc: Use PPC2_ISA207 instead of PPC2_BCTAR_ISA207 Chinmay Rath
2026-08-17 15:24   ` Miles Glenn
2026-07-15 12:56 ` [PATCH 3/7] target/ppc: Use PPC2_ISA207 instead of PPC2_LSQ_ISA207 Chinmay Rath
2026-08-17 15:25   ` Miles Glenn
2026-07-15 12:56 ` [PATCH 4/7] target/ppc: Use PPC2_ISA207 instead of PPC2_ALTIVEC_207 Chinmay Rath
2026-08-17 15:27   ` Miles Glenn
2026-07-15 12:56 ` [PATCH 5/7] target/ppc: Use PPC2_ISA207 instead of PPC2_ISA207S Chinmay Rath
2026-08-17 15:28   ` Miles Glenn
2026-07-15 12:56 ` [PATCH 6/7] target/ppc: Reorder PPC2 flags Chinmay Rath
2026-07-15 14:41   ` Shivang Upadhyay
2026-07-20 13:05     ` Chinmay Rath
2026-08-17 15:44       ` Miles Glenn [this message]
2026-07-15 12:56 ` [PATCH 7/7] target/ppc: Add ICBT support for ISA version 2.07 Chinmay Rath
2026-08-17 11:30   ` tasmiya
2026-08-17 15:56   ` Miles Glenn
2026-08-18  7:03     ` Chinmay Rath
2026-08-18 15:24       ` Miles Glenn

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=e4f97605390ec0829c0ae757d6e7edabf701b78e.camel@linux.ibm.com \
    --to=milesg@linux.ibm.com \
    --cc=harshpb@linux.ibm.com \
    --cc=npiggin@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=rathc@linux.ibm.com \
    --cc=richard.henderson@linaro.org \
    --cc=shivangu@linux.ibm.com \
    --cc=tommusta@gmail.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.