xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Jason Andryuk <jandryuk@gmail.com>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Juergen Gross <jgross@suse.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] xen: Remove Xen PVH/PVHVM dependency on PCI
Date: Thu, 15 Oct 2020 10:10:11 +0200	[thread overview]
Message-ID: <b74a3f83-cd8a-34a3-b436-95141f01cb20@suse.com> (raw)
In-Reply-To: <20201014175342.152712-2-jandryuk@gmail.com>

On 14.10.2020 19:53, Jason Andryuk wrote:
> @@ -76,7 +80,9 @@ config XEN_DEBUG_FS
>  	  Enabling this option may incur a significant performance overhead.
>  
>  config XEN_PVH
> -	bool "Support for running as a Xen PVH guest"
> +	bool "Xen PVH guest support"

Tangential question: Is "guest" here still appropriate, i.e.
isn't this option also controlling whether the kernel can be
used in a PVH Dom0?

>  	def_bool n

And is this default still appropriate?

Jan


  reply	other threads:[~2020-10-15  8:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-14 17:53 [PATCH 0/2] Remove Xen PVH dependency on PCI Jason Andryuk
2020-10-14 17:53 ` [PATCH 1/2] xen: Remove Xen PVH/PVHVM " Jason Andryuk
2020-10-15  8:10   ` Jan Beulich [this message]
2020-10-15 14:59     ` Jason Andryuk
2020-10-15 15:02       ` Jan Beulich
2020-10-15 15:08         ` Roger Pau Monné
2020-10-14 17:53 ` [PATCH 2/2] xen: Kconfig: nest Xen guest options Jason Andryuk
2020-10-15  9:41   ` Jürgen Groß
2020-10-15 14:52     ` Jason Andryuk
2020-10-15 12:37   ` boris.ostrovsky
2020-10-15 13:10     ` Andrew Cooper
2020-10-15 13:17       ` boris.ostrovsky
2020-10-15 14:50         ` Jason Andryuk
2020-10-14 18:04 ` [SUSPECTED SPAM][PATCH 0/2] Remove Xen PVH dependency on PCI Andrew Cooper
2020-10-14 19:31   ` Jason Andryuk
2020-12-16  7:01 ` [PATCH " Jürgen Groß

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=b74a3f83-cd8a-34a3-b436-95141f01cb20@suse.com \
    --to=jbeulich@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=jandryuk@gmail.com \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=sstabellini@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@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).