[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 2/6] x86/feature: Generalise synth and introduce a bug word

To: "Andrew Cooper" <andrew.cooper3@xxxxxxxxxx>
From: "Jan Beulich" <JBeulich@xxxxxxxx>
Date: Tue, 08 Jan 2019 09:20:46 -0700
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxx>, Wei Liu <wei.liu2@xxxxxxxxxx>, Roger Pau Monne <roger.pau@xxxxxxxxxx>
Delivery-date: Tue, 08 Jan 2019 16:20:59 +0000
List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

>>> On 28.12.18 at 13:39, <andrew.cooper3@xxxxxxxxxx> wrote:
> Future changes are going to want to use cpu_bug_* in a mannor similar to
> Linux.  Introduce one bug word, and generalise the calculation of
> NCAPINTS.

As said elsewhere, unless for the purpose of alternatives patching
I'm not convinced of the benefits of this over simple boolean
variables.

Jan



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

Prev by Date: Re: [Xen-devel] [PATCH 1/6] x86/AMD Split init_amd() into per-uarch helpers
Next by Date: Re: [Xen-devel] [RFC PATCH 2/6] tools/libxc: Define VM_EVENT type
Previous by thread: Re: [Xen-devel] [PATCH 2/6] x86/feature: Generalise synth and introduce a bug word
Next by thread: Re: [Xen-devel] [PATCH 4/6] x86/AMD: Introduce and use X86_BUG_NULL_SEG
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.