Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Jan Beulich <jbeulich@suse.com>
Subject: [PATCH v2 0/9] xen/x86: PVH Dom0 fixes and fallout adjustments
To:     Juergen Gross <jgross@suse.com>,
        Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc:     Stefano Stabellini <sstabellini@kernel.org>,
        lkml <linux-kernel@vger.kernel.org>,
        =?UTF-8?Q?Roger_Pau_Monn=c3=a9?= <roger.pau@citrix.com>,
        "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Message-ID: <9a26d4ff-80a1-e0c1-f528-31a8568d41f7@suse.com>
Date:   Thu, 30 Sep 2021 14:12:31 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.14.0
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: =?utf-8?B?TEVSVzFiWnFIVFdDS3RPdFhkMmxuKzdMam5sd1IyT1B3dzdyR3dIeWJPdzF2?=
 =?utf-8?B?dTNtbmpTOWlpelBYekl0eG90SXgzYSsyVWg3clllbG43WTNqR0dCRTFZdUNp?=
 =?utf-8?B?bFpKQ3dNTEE2MDlBSWRVWHcyTnhVdE10clVvd1VMZC85QXBTbEEzdTNwUVlP?=
 =?utf-8?B?N0lYRElFV0R1OFBQc2JxSS9YcTlKTEpFZjNqZ3RMajFOVUIrYmxvelVKamtO?=
 =?utf-8?B?QVlBLzFIM0VFMzZRbGVTNDMvSnpxNmdNMndRMGxsQXRVMWNyc0cwRjVkaDU3?=
 =?utf-8?B?SFhDTjRuVzFxTzNIcVorZUhDTmQ2L1hJdnZoZnBzUGoxS3dlMUsvYXZENUZp?=
 =?utf-8?B?eUwvdlh6U3o4NGlmajE4UURYMWdQNmdEOXlxOWVqSnkxWExnQlIrZjk4Vzlj?=
 =?utf-8?B?SlUyZFNCaVR5cWhRbmIwTkRCM3Ntc3JJbXNaWW9YMkJWZkpMTWM3RDU0OVVS?=
 =?utf-8?B?d2tFYmxqeFM5dVFBSXdMb1pPUmZJQ0t3aURrNTJ3TmU5Vjg3NlNoQVNURVJi?=
 =?utf-8?B?amtUUWZ1S0l0TzdPZS9NVlBBbWFVUEZGUFdFNGk0MVRlT2hBRnFxU1BTdGFG?=
 =?utf-8?B?emovSUZnNWRSZ29qYUVLUTNuVThzZHpxQ2tNeE5CL1V6SUhvRlJXbGlHa2Yy?=
 =?utf-8?B?d3VCcXgzVjZidlU0WDB2cmNTVys4ZTAyNytGanVZbEJtbHFUSXVzblBMSUhu?=
 =?utf-8?B?cjZTZDIyVFBWclVKQVhJa0hiUFptaUpXc0FkSVVvMG5QTW9BMitJWVFPMnFQ?=
 =?utf-8?B?TkpSaUFoZGJ3amVQVWtocjhqNXB0VE9PV0V0ejUxVUZweHlGNFI1c3lPTDJE?=
 =?utf-8?B?czZ0Ky9va0dPRDkxRFFoQ3NsR2N1YkVwSTZZajF0a2tneXIxWDFvMGN4bm1H?=
 =?utf-8?B?MitaU3pLQ2dRaEYweU93UHhlZmFlMnk5bTZOeUowUUI5YWhZaVJtS09NV0F4?=
 =?utf-8?B?Wlg3YThlcG9aVGU4UnR1ZHZZaGR2KzRBZjF1Rmw1WGIzUmRlKzM2Y1J3R2JX?=
 =?utf-8?B?TXJUR3A4TE8wRDM2VWU2clYwUVNZSllnK3VFWTZkVUpPZHBJVC9jQlo2VjJB?=
 =?utf-8?B?K21HWGtrUlhzWjZja3p5NlUvV0EzanJFK2dXVnVXVXRUY3lXN1cxbEpaclpa?=
 =?utf-8?B?bTVpakpWWW52NWN1UThEVlZYMXpNTTJlY0E0VkZudlA0eU9SdXhkZG1IaDJ6?=
 =?utf-8?B?UFFZbFRNb3FFa2ZNZDY1UHBubWhkWWI1a3FybXZ1M3RUb0VOVEg0Qzl2amVD?=
 =?utf-8?B?OG1YaDd2MVl5ays1TGV3cXZmcGJ6L0RHZEJwUUt0Y0sxcXpEMlhaSmVEckFD?=
 =?utf-8?B?dVFDZm1PR2VYVGRUSGtrd0c4MnhwdGt1YTlIaEtIL1Fzc0YwcmxXTWp2NHRX?=
 =?utf-8?B?bTZsRFNqNTlwWHF1TWtQK0p0dE12d3h1MzlxejlhdDk0RW9uLyt3dVNrUjN1?=
 =?utf-8?B?TTMyVTdGbHNCQXI0RmFUTUVpMlI3VmwvR0M1V214MUhTMnkvSmhVUXBHRElz?=
 =?utf-8?B?T3Z1N3BZUGFLMFZWNXYwNkRXUFhXN3BuTFRqNGczM2VDUTBPZ1Nzbk1QRmdP?=
 =?utf-8?B?bVZoRlYwcVNQdFM4NFloQktEVkFZaThJenVIOTE5b2Y3YTRudGdCWHJqRmtz?=
 =?utf-8?B?NjZtVWQrV3loS0t3dzY4VFY4SXB0eHBJNkdQUDhyOXdEdmRHUHl6NXdoejdN?=
 =?utf-8?B?TUUxcVYrWHJNK1RpNy9UaGo5RUlwRzlyaFFPL0V6eUNkNXpSdG8vNzNnekQ4?=
 =?utf-8?Q?aXsJHbJ6Ar011t4nWode5ixf+gCgZTOzXpZyDqp?=
X-OriginatorOrg: suse.com
X-MS-Exchange-CrossTenant-Network-Message-Id: ae202350-3d4f-4be3-939b-08d9840b951a
X-MS-Exchange-CrossTenant-AuthSource: VI1PR04MB5600.eurprd04.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 30 Sep 2021 12:12:33.1758
 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: f7a17af6-1c5c-4a36-aa8b-f5be247aa4ba
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: XxWRJUU7dRPfmjmjzvXaaWx/SV972jQGpT4qIg6Bh93Yd0iwDXHzbxo3mA3jZUkY+k29WtjCkt2yAiZZDOWmrw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VE1PR04MB6382
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

In order to try to debug hypervisor side breakage from XSA-378 I found
myself urged to finally give PVH Dom0 a try. Sadly things didn't work
quite as expected. In the course of investigating these issues I actually
spotted one piece of PV Dom0 breakage as well, a fix for which is also
included here.

There are one immediate remaining issues: Dom0, unlike in the PV case,
cannot access the screen (to use as a console) when in a non-default
mode (i.e. not 80x25 text), as the necessary information (in particular
about VESA-bases LFB modes) is not communicated. On the hypervisor side
this looks like deliberate behavior, but it is unclear to me what the
intentions were towards an alternative model. (X may be able to access
the screen depending on whether it has a suitable driver besides the
presently unusable /dev/fb<N> based one.)

v2 merely addresses small review comments in patches 7 and 9 (see there).

1: xen/x86: prevent PVH type from getting clobbered
2: xen/x86: allow PVH Dom0 without XEN_PV=y
3: xen/x86: make "earlyprintk=xen" work better for PVH Dom0
4: xen/x86: allow "earlyprintk=xen" to work for PV Dom0
5: xen/x86: make "earlyprintk=xen" work for HVM/PVH DomU
6: xen/x86: generalize preferred console model from PV to PVH Dom0
7: xen/x86: hook up xen_banner() also for PVH 
8: x86/PVH: adjust function/data placement
9: xen/x86: adjust data placement

Jan