On 10/04/18 11:36, Jan Beulich wrote:
On 10.04.18 at 11:32, wrote:
>> On 10/04/18 11:14, Jan Beulich wrote:
>> On 10.04.18 at 09:58, wrote:
--- a/docs/misc/xen-command-line.markdown
+++ b/docs/misc/xen-command-line.markdown
@@ -1955,14 +1955,29 @@ clustered mode. The defa
>>> On 10.04.18 at 11:32, wrote:
> On 10/04/18 11:14, Jan Beulich wrote:
> On 10.04.18 at 09:58, wrote:
>>> --- a/docs/misc/xen-command-line.markdown
>>> +++ b/docs/misc/xen-command-line.markdown
>>> @@ -1955,14 +1955,29 @@ clustered mode. The default, given no hint from
>>> the **FADT**, i
On 10/04/18 11:14, Jan Beulich wrote:
On 10.04.18 at 09:58, wrote:
>> --- a/docs/misc/xen-command-line.markdown
>> +++ b/docs/misc/xen-command-line.markdown
>> @@ -1955,14 +1955,29 @@ clustered mode. The default, given no hint from the
>> **FADT**, is cluster
>> mode.
>>
>> ### xpti
>>
>>> On 10.04.18 at 09:58, wrote:
> --- a/docs/misc/xen-command-line.markdown
> +++ b/docs/misc/xen-command-line.markdown
> @@ -1955,14 +1955,29 @@ clustered mode. The default, given no hint from the
> **FADT**, is cluster
> mode.
>
> ### xpti
> -> `= `
> +> `= List of [ default | | dom0= |
Instead of switching XPTI globally on or off add a per-domain flag for
that purpose. This allows to modify the xpti boot parameter to support
running dom0 without Meltdown mitigations. Using "xpti=nodom0" as boot
parameter will achieve that.
Move the xpti boot parameter handling to xen/arch/x86/pv
