linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Jan Beulich <jbeulich@suse.com>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: "Stefano Stabellini" <sstabellini@kernel.org>,
	lkml <linux-kernel@vger.kernel.org>,
	"Roger Pau Monné" <roger.pau@citrix.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v2 0/9] xen/x86: PVH Dom0 fixes and fallout adjustments
Date: Tue, 5 Oct 2021 08:38:53 +0200	[thread overview]
Message-ID: <e3f4db18-fe1b-ef73-84d6-a3351d83f8f3@suse.com> (raw)
In-Reply-To: <9a26d4ff-80a1-e0c1-f528-31a8568d41f7@suse.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 1553 bytes --]

On 30.09.21 14:12, Jan Beulich wrote:
> 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

Series pushed to xen/tip.git for-linus-5.15b


Juergen


[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3135 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

      parent reply	other threads:[~2021-10-05  6:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-30 12:12 [PATCH v2 0/9] xen/x86: PVH Dom0 fixes and fallout adjustments Jan Beulich
2021-09-30 12:16 ` [PATCH v2 1/9] xen/x86: prevent PVH type from getting clobbered Jan Beulich
2021-09-30 12:16 ` [PATCH v2 2/9] xen/x86: allow PVH Dom0 without XEN_PV=y Jan Beulich
2021-09-30 12:17 ` [PATCH v2 3/9] xen/x86: make "earlyprintk=xen" work better for PVH Dom0 Jan Beulich
2021-09-30 12:18 ` [PATCH v2 4/9] xen/x86: allow "earlyprintk=xen" to work for PV Dom0 Jan Beulich
2021-09-30 12:18 ` [PATCH v2 5/9] xen/x86: make "earlyprintk=xen" work for HVM/PVH DomU Jan Beulich
2021-09-30 12:19 ` [PATCH v2 6/9] xen/x86: generalize preferred console model from PV to PVH Dom0 Jan Beulich
2021-09-30 12:19 ` [PATCH v2 7/9] xen/x86: hook up xen_banner() also for PVH Jan Beulich
2021-09-30 12:45   ` Juergen Gross
2021-09-30 12:20 ` [PATCH v2 8/9] x86/PVH: adjust function/data placement Jan Beulich
2021-09-30 12:21 ` [PATCH v2 9/9] xen/x86: adjust data placement Jan Beulich
2021-09-30 12:45   ` Juergen Gross
2021-10-05  6:38 ` Juergen Gross [this message]

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=e3f4db18-fe1b-ef73-84d6-a3351d83f8f3@suse.com \
    --to=jgross@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jbeulich@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@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).