qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "ishii.shuuichir@fujitsu.com" <ishii.shuuichir@fujitsu.com>
To: "'Alex Bennée'" <alex.bennee@linaro.org>
Cc: "peter.maydell@linaro.org" <peter.maydell@linaro.org>,
	"qemu-arm@nongnu.org" <qemu-arm@nongnu.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"ishii.shuuichir@fujitsu.com" <ishii.shuuichir@fujitsu.com>
Subject: RE: [PATCH v2 1/3] target-arm: delete ARM_FEATURE_A64FX
Date: Tue, 3 Aug 2021 00:32:01 +0000	[thread overview]
Message-ID: <TYCPR01MB61601C4DE620EE9EE5AB2FB0E9F09@TYCPR01MB6160.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <87r1fggka6.fsf@linaro.org>


> This is confusing because I can't see this feature flag in the mainline branch. Have
> you inadvertently based this series from an internal branch?

I'm sorry for the confusion.

My lack of understanding of how to handle v2 patches has led me to create a v2 patch series
based on patches that have not been merged into upstream.
I will repost this so that the implementation can be closed in one patch series.

Best regards.
> -----Original Message-----
> From: Alex Bennée <alex.bennee@linaro.org>
> Sent: Friday, July 30, 2021 7:36 PM
> To: Ishii, Shuuichirou/石井 周一郎 <ishii.shuuichir@fujitsu.com>
> Cc: peter.maydell@linaro.org; qemu-devel@nongnu.org; qemu-arm@nongnu.org
> Subject: Re: [PATCH v2 1/3] target-arm: delete ARM_FEATURE_A64FX
> 
> 
> Shuuichirou Ishii <ishii.shuuichir@fujitsu.com> writes:
> 
> > The ARM_FEATURE_A64FX property was added, but there is no function
> > that uses this property yet, so it will be removed until a function
> > that uses it is added.
> >
> > Signed-off-by: Shuuichirou Ishii <ishii.shuuichir@fujitsu.com>
> > ---
> >  target/arm/cpu.h   | 1 -
> >  target/arm/cpu64.c | 1 -
> >  2 files changed, 2 deletions(-)
> >
> > diff --git a/target/arm/cpu.h b/target/arm/cpu.h index
> > 1b0c7b91ec..9f0a5f84d5 100644
> > --- a/target/arm/cpu.h
> > +++ b/target/arm/cpu.h
> > @@ -2145,7 +2145,6 @@ enum arm_features {
> >      ARM_FEATURE_M_SECURITY, /* M profile Security Extension */
> >      ARM_FEATURE_M_MAIN, /* M profile Main Extension */
> >      ARM_FEATURE_V8_1M, /* M profile extras only in v8.1M and later */
> > -    ARM_FEATURE_A64FX, /* Fujitsu A64FX processor HPC extensions
> > support */
> 
> This is confusing because I can't see this feature flag in the mainline branch. Have
> you inadvertently based this series from an internal branch?
> 
> >  };
> >
> >  static inline int arm_feature(CPUARMState *env, int feature) diff
> > --git a/target/arm/cpu64.c b/target/arm/cpu64.c index
> > a15f9c0c55..dd72300e88 100644
> > --- a/target/arm/cpu64.c
> > +++ b/target/arm/cpu64.c
> > @@ -856,7 +856,6 @@ static void aarch64_a64fx_initfn(Object *obj)
> >      ARMCPU *cpu = ARM_CPU(obj);
> >
> >      cpu->dtb_compatible = "arm,a64fx";
> > -    set_feature(&cpu->env, ARM_FEATURE_A64FX);
> >      set_feature(&cpu->env, ARM_FEATURE_V8);
> >      set_feature(&cpu->env, ARM_FEATURE_NEON);
> >      set_feature(&cpu->env, ARM_FEATURE_GENERIC_TIMER);
> 
> 
> --
> Alex Bennée

  reply	other threads:[~2021-08-03  0:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-30  3:08 [PATCH v2 0/3] Add support for Fujitsu A64FX processor Shuuichirou Ishii
2021-07-30  3:08 ` [PATCH v2 1/3] target-arm: delete ARM_FEATURE_A64FX Shuuichirou Ishii
2021-07-30 10:34   ` Peter Maydell
2021-08-03  0:23     ` ishii.shuuichir
2021-07-30 10:36   ` Alex Bennée
2021-08-03  0:32     ` ishii.shuuichir [this message]
2021-07-30  3:08 ` [PATCH v2 2/3] target-arm: cpu64: Add support for Fujitsu A64FX Shuuichirou Ishii
2021-07-30  3:08 ` [PATCH v2 3/3] target-arm: Add A64FX processor support to virt machine Shuuichirou Ishii
2021-07-30 10:36   ` Peter Maydell
2021-08-03  0:21     ` ishii.shuuichir
2021-07-30 10:38 ` [PATCH v2 0/3] Add support for Fujitsu A64FX processor Peter Maydell
2021-08-03  0:36   ` ishii.shuuichir
2021-08-03  9:03     ` Peter Maydell

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=TYCPR01MB61601C4DE620EE9EE5AB2FB0E9F09@TYCPR01MB6160.jpnprd01.prod.outlook.com \
    --to=ishii.shuuichir@fujitsu.com \
    --cc=alex.bennee@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@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).