From: Pu Wen <puwen@hygon.cn>
To: Jan Beulich <jbeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Brian Woods <brian.woods@amd.com>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [PATCH v4 00/15] Add support for Hygon Dhyana Family 18h processor
Date: Wed, 3 Apr 2019 23:21:03 +0800 [thread overview]
Message-ID: <1eb44fcb-6cf1-3f1c-f5c5-70a235149d00@hygon.cn> (raw)
In-Reply-To: <5CA38A8D0200007800223FC4@prv1-mh.provo.novell.com>
On 2019/4/3 0:15, Jan Beulich wrote:
> On 02.04.19 at 18:00, <puwen@hygon.cn> wrote:
>> On 2019/4/2 23:14, Andrew Cooper wrote:
>>> On 30/03/2019 10:40, Pu Wen wrote:
>>>> This patch series have been applied and tested successfully on Hygon
>>>> Dhyana processor, also been tested on AMD EPYC (family 17h) processor.
>>>> It works fine and makes no harm to the existing code.
>>> One thing I don't see in this series is anything about microcode
>>> loading. Presumably you'll follow the AMD patchloading mechanism, with
>>> a blob you provide yourself?
>> When the Hygon patchloading mechanism is practicable and it's necessary
>> to load the Hygon microcode outside of BIOS, we'll send the patchloading
>> patches to Xen and Linux mailing lists.
>
> I suppose both Intel and AMD had this same intention of ucode loading
> being a firmware job only, and we see where we are right now. As long
> as updated firmware does not become available in a timely manner (or
> perhaps not at all, because of a vendor considering a certain system
> EOL), there's going to be a need to be able to load it from the OS.
It's reasonable. But I'll not put the microcode loading patch in this
series, and will sent it individually later after sufficiently tested.
Or just add Hygon vendor checking to follow the AMD patchloading
mechanism right now and do the adjustment for Hygon if needed in the
future?
--
Regards,
Pu Wen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-04-03 15:30 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-30 10:40 [PATCH v4 00/15] Add support for Hygon Dhyana Family 18h processor Pu Wen
2019-03-30 10:42 ` [PATCH v4 01/15] x86/cpu: Create Hygon Dhyana architecture support file Pu Wen
2019-04-02 12:13 ` Andrew Cooper
2019-04-02 13:09 ` Pu Wen
2019-04-03 8:42 ` Jan Beulich
2019-04-03 10:05 ` Pu Wen
2019-04-03 10:21 ` Jan Beulich
2019-04-03 15:27 ` Pu Wen
2019-03-30 10:42 ` [PATCH v4 02/15] x86/cpu: Fix common cpuid faulting probing for AMD and Hygon Pu Wen
2019-04-01 8:40 ` Jan Beulich
2019-04-02 6:46 ` Pu Wen
2019-04-02 10:19 ` Jan Beulich
2019-04-02 11:58 ` Pu Wen
2019-04-02 15:46 ` Jan Beulich
2019-04-02 15:49 ` Andrew Cooper
2019-04-02 16:14 ` Pu Wen
2019-04-02 17:04 ` Andrew Cooper
2019-04-02 10:30 ` Andrew Cooper
2019-04-02 15:44 ` Jan Beulich
2019-03-30 10:42 ` [PATCH v4 03/15] x86/cpu/mtrr: Add Hygon Dhyana support to get TOP_MEM2 Pu Wen
2019-03-30 10:42 ` [PATCH v4 04/15] x86/cpu/vpmu: Add Hygon Dhyana and AMD Zen support for vPMU Pu Wen
2019-04-01 8:35 ` Jan Beulich
2019-04-02 6:46 ` Pu Wen
2019-04-02 10:20 ` Jan Beulich
2019-04-02 12:11 ` Pu Wen
2019-04-02 15:50 ` Jan Beulich
2019-04-02 16:26 ` Pu Wen
2019-03-30 10:43 ` [PATCH v4 05/15] x86/cpu/mce: Add Hygon Dhyana support to the MCA infrastructure Pu Wen
2019-03-30 10:43 ` [PATCH v4 06/15] x86/spec_ctrl: Add Hygon Dhyana to the respective mitigation machinery Pu Wen
2019-03-30 10:43 ` [PATCH v4 07/15] x86/apic: Add Hygon Dhyana support Pu Wen
2019-03-30 10:43 ` [PATCH v4 08/15] x86/acpi: " Pu Wen
2019-03-30 10:44 ` [PATCH v4 09/15] x86/iommu: " Pu Wen
2019-03-30 10:44 ` [PATCH v4 10/15] x86/pv: Add Hygon Dhyana support to emulate MSRs access Pu Wen
2019-03-30 10:44 ` [PATCH v4 11/15] x86/domain: Add Hygon Dhyana support Pu Wen
2019-03-30 10:44 ` [PATCH v4 12/15] x86/domctl: " Pu Wen
2019-03-30 10:44 ` [PATCH v4 13/15] x86/traps: " Pu Wen
2019-03-30 10:44 ` [PATCH v4 14/15] x86/cpuid: " Pu Wen
2019-03-30 10:44 ` [PATCH v4 15/15] tools/libxc: " Pu Wen
2019-04-02 15:00 ` [PATCH v4 00/15] Add support for Hygon Dhyana Family 18h processor Andrew Cooper
2019-04-02 16:00 ` Pu Wen
2019-04-02 16:15 ` Jan Beulich
2019-04-03 15:21 ` Pu Wen [this message]
2019-04-03 15:33 ` Jan Beulich
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=1eb44fcb-6cf1-3f1c-f5c5-70a235149d00@hygon.cn \
--to=puwen@hygon.cn \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=brian.woods@amd.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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 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.