From: "H.J. Lu" <hjl.tools@gmail.com>
To: mayshao-oc <mayshao-oc@zhaoxin.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
"Carlos O'Donell" <carlos@redhat.com>,
Florian Weimer <fw@deneb.enyo.de>,
"Qiyuan Wang(BJ-RD)" <QiyuanWang@zhaoxin.com>,
"Herry Yang(BJ-RD)" <HerryYang@zhaoxin.com>,
"Ricky Li(BJ-RD)" <RickyLi@zhaoxin.com>
Subject: Re: [PATCH v3 3/3] x86: Add the test case of __get_cpu_features support for Zhaoxin processors
Date: Fri, 24 Apr 2020 05:54:02 -0700 [thread overview]
Message-ID: <CAMe9rOoe6r9rKC=vv7G0smL9DAsYX-xy6_Mh44SzEPU1QwG51g@mail.gmail.com> (raw)
In-Reply-To: <1587731372-9324-4-git-send-email-mayshao-oc@zhaoxin.com>
On Fri, Apr 24, 2020 at 5:29 AM mayshao-oc <mayshao-oc@zhaoxin.com> wrote:
>
> From: mayshao <mayshao-oc@zhaoxin.com>
>
> For the test case of the __get_cpu_features interface, add an item in
> cpu_kinds and a switch case for Zhaoxin support.
> ---
> sysdeps/x86/tst-get-cpu-features.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/sysdeps/x86/tst-get-cpu-features.c b/sysdeps/x86/tst-get-cpu-features.c
> index 0f55987..0dcb906 100644
> --- a/sysdeps/x86/tst-get-cpu-features.c
> +++ b/sysdeps/x86/tst-get-cpu-features.c
> @@ -38,6 +38,7 @@ static const char * const cpu_kinds[] =
> "Unknown",
> "Intel",
> "AMD",
> + "ZHAOXIN",
> "Other",
> };
>
> @@ -50,6 +51,7 @@ do_test (void)
> {
> case arch_kind_intel:
> case arch_kind_amd:
> + case arch_kind_zhaoxin:
> case arch_kind_other:
> printf ("Vendor: %s\n", cpu_kinds[cpu_features->basic.kind]);
> printf ("Family: 0x%x\n", cpu_features->basic.family);
> --
> 2.7.4
>
LGTM.
--
H.J.
prev parent reply other threads:[~2020-04-24 12:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 12:29 [PATCH v3 0/3] x86: Add " mayshao-oc
2020-04-24 12:29 ` [PATCH v3 1/3] x86: Add CPU Vendor ID detection " mayshao-oc
2020-04-24 12:53 ` H.J. Lu
2020-04-24 12:29 ` [PATCH v3 2/3] x86: Add cache information " mayshao-oc
2020-04-24 12:53 ` H.J. Lu
2020-04-26 5:54 ` Mayshao-oc
2020-04-26 12:07 ` H.J. Lu
2020-04-30 5:09 ` Mayshao-oc
2020-04-30 5:15 ` H.J. Lu
2020-04-30 6:04 ` Mayshao-oc
2020-04-30 12:52 ` H.J. Lu
2020-04-30 13:22 ` Mayshao-oc
2020-04-30 13:55 ` H.J. Lu
2020-04-30 14:39 ` Mayshao-oc
2020-04-30 19:10 ` Joseph Myers
2020-04-30 19:16 ` Florian Weimer
2020-04-30 19:21 ` H.J. Lu
2020-04-30 20:04 ` Florian Weimer
2020-04-24 12:29 ` [PATCH v3 3/3] x86: Add the test case of __get_cpu_features " mayshao-oc
2020-04-24 12:54 ` H.J. Lu [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='CAMe9rOoe6r9rKC=vv7G0smL9DAsYX-xy6_Mh44SzEPU1QwG51g@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=HerryYang@zhaoxin.com \
--cc=QiyuanWang@zhaoxin.com \
--cc=RickyLi@zhaoxin.com \
--cc=carlos@redhat.com \
--cc=fw@deneb.enyo.de \
--cc=libc-alpha@sourceware.org \
--cc=mayshao-oc@zhaoxin.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 read-only IMAP folder(s) and NNTP newsgroup(s).