From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Juergen Gross <jgross@suse.com>,
the arch/x86 maintainers <x86@kernel.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH 2/3] xen/mcelog: add PPIN to record when available
Date: Wed, 13 Nov 2019 11:34:55 -0500 [thread overview]
Message-ID: <e3409dfb-3d81-e06f-192b-bb4a3546c628@oracle.com> (raw)
In-Reply-To: <5f8bbcb2-2eb9-c9f4-622a-43a6d0814b94@suse.com>
On 11/13/19 8:44 AM, Jan Beulich wrote:
> On 13.11.2019 01:11, Boris Ostrovsky wrote:
>> On 11/11/19 9:46 AM, Jan Beulich wrote:
>>> --- a/arch/x86/include/asm/msr-index.h
>>> +++ b/arch/x86/include/asm/msr-index.h
>>> @@ -393,6 +393,8 @@
>>> #define MSR_AMD_PSTATE_DEF_BASE 0xc0010064
>>> #define MSR_AMD64_OSVW_ID_LENGTH 0xc0010140
>>> #define MSR_AMD64_OSVW_STATUS 0xc0010141
>>> +#define MSR_AMD_PPIN_CTL 0xc00102f0
>>> +#define MSR_AMD_PPIN 0xc00102f1
>> Which processors are these defined for? I looked at a couple (fam 15h
>> and 17h) and didn't see those. And I don't see them in Linux.
> Certain Fam17 ones, Rome in particular (which is where I've
> tested this).
I was looking at Naples, can't find Rome on AMD's page.
>
>>> --- a/include/xen/interface/xen-mca.h
>>> +++ b/include/xen/interface/xen-mca.h
>>> @@ -332,7 +332,11 @@ struct xen_mc {
>>> };
>>> DEFINE_GUEST_HANDLE_STRUCT(xen_mc);
>>>
>>> -/* Fields are zero when not available */
>>> +/*
>>> + * Fields are zero when not available. Also, this struct is shared with
>>> + * userspace mcelog and thus must keep existing fields at current offsets.
>>> + * Only add new fields to the end of the structure
>>> + */
>>> struct xen_mce {
>> Why is this structure is part of the interface?
> That's a question to whoever put it there. There look to have
> been decisions (see also patch 1) to have the Linux clones of
> Xen's public headers deviate far more from their original
> than I would consider reasonable.
Yes, this goes back to when the file was first created.
Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
(but if you want to move non-interface parts into, say,
drivers/xen/mcelog.h I won't stand in your way ;-) )
next prev parent reply other threads:[~2019-11-13 16:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 14:43 [PATCH 0/3] xen/mcelog: assorted adjustments Jan Beulich
2019-11-11 14:45 ` [PATCH 1/3] xen/mcelog: drop __MC_MSR_MCGCAP Jan Beulich
2019-11-12 23:55 ` Boris Ostrovsky
2019-11-11 14:46 ` [PATCH 2/3] xen/mcelog: add PPIN to record when available Jan Beulich
2019-11-13 0:11 ` Boris Ostrovsky
2019-11-13 13:44 ` [Xen-devel] " Jan Beulich
2019-11-13 16:34 ` Boris Ostrovsky [this message]
2019-11-11 14:46 ` [PATCH 3/3] xen/mcelog: also allow building for 32-bit kernels Jan Beulich
2019-11-13 0:15 ` Boris Ostrovsky
2019-11-13 13:47 ` [Xen-devel] " Jan Beulich
2019-11-13 14:06 ` Jürgen Groß
2019-11-14 7:54 ` Jürgen Groß
2019-11-14 13:05 ` [PATCH 0/3] xen/mcelog: assorted adjustments Jürgen Groß
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=e3409dfb-3d81-e06f-192b-bb4a3546c628@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.org \
--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 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).