All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ahmed S. Darwish" <darwi@linutronix.de>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Sohil Mehta <sohil.mehta@intel.com>,
	x86-cpuid@lists.linux.dev, Thomas Gleixner <tglx@linutronix.de>,
	Xin Li <xin@zytor.com>, "H . Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] db: Add Intel NMI-source reporting feature flag
Date: Thu, 26 Sep 2024 21:57:25 +0200	[thread overview]
Message-ID: <ZvW8pRCqV64eGk8q@lx-t490> (raw)
In-Reply-To: <27d8c0ed-62ae-4956-93d4-f68e554fedab@citrix.com>

On Thu, 26 Sep 2024, Andrew Cooper wrote:
>
> I guess I need to start getting back to this...
>
> The Xen 'attrs' need stripping. More specifically, they need to live in
> Xen itself, because they are different by release, and are used in the
> derivation of what is safe to offer to guests.
>
> But the same is true for 'feature' too.  It's one think to know what the
> bit means, but it's something else to be making a statement about what
> is supported in an external project.
>
> When this is used in earnest, regenerating the headers will be needed in
> each stable tree to get e.g. the new speculation (anti)features, and
> doing so needs to not change the other features="true" for bits only
> supported in newer branches.
>

Yeah, correct.

I still remember our discussion on how the <xen> tag (and its
attributes) were not fitting Xen's model.  So, for now, it's indeed a
placeholder until work starts earnestly on that part.

Thanks,
Ahmed

--
Linutronix GmbH

  reply	other threads:[~2024-09-26 19:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-23 22:32 [PATCH] db: Add Intel NMI-source reporting feature flag Sohil Mehta
2024-09-23 22:57 ` Sohil Mehta
2024-09-26 13:12   ` Ahmed S. Darwish
2024-09-26 15:33     ` Andrew Cooper
2024-09-26 19:57       ` Ahmed S. Darwish [this message]
2024-09-27 17:47     ` Sohil Mehta
2024-09-27 18:29       ` H. Peter Anvin
2024-09-27 18:55         ` Sohil Mehta
2024-09-28  7:34         ` Ahmed S. Darwish
2024-09-24 16:09 ` Ahmed S. Darwish

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=ZvW8pRCqV64eGk8q@lx-t490 \
    --to=darwi@linutronix.de \
    --cc=andrew.cooper3@citrix.com \
    --cc=hpa@zytor.com \
    --cc=sohil.mehta@intel.com \
    --cc=tglx@linutronix.de \
    --cc=x86-cpuid@lists.linux.dev \
    --cc=xin@zytor.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.