mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Maran Wilson <maran.wilson@oracle.com>,
	pbonzini@redhat.com, jgross@suse.com, roger.pau@citrix.com,
	andrew.cooper3@citrix.com, hch@infradead.org, x86@kernel.org,
	xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
	kvm@vger.kernel.org
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
	rkrcmar@redhat.com, JBeulich@suse.com
Subject: Re: [RFC PATCH v2 0/2] KVM: x86: Allow Qemu/KVM to use PVH entry point
Date: Fri, 8 Dec 2017 14:21:45 -0500	[thread overview]
Message-ID: <a506ad26-5e33-d99d-64a8-cefc3fa42c87@oracle.com> (raw)
In-Reply-To: <1512686715-11488-1-git-send-email-maran.wilson@oracle.com>

On 12/07/2017 05:45 PM, Maran Wilson wrote:
>
> Juergen also had a suggestion to split the different hypervisor types
> early and use a common set of service functions instead of special casing
> xen_guest everywhere.
>
> There are certainly less special cases in this version of the patch, but
> if we still think it's important to split things up between common, Xen,
> and KVM components, then I would appreciate a suggestion on how best that
> can be done. Are we talking about just re-factoring functions in the
> existing file? Or do we need to go all the way and pull all the PVH entry
> code out of xen directories and find a home for it somewhere else so that
> we can use kernels built without CONFIG_XEN to start KVM guests via the
> PVH entry point. If the latter, any suggestions for which common files or
> directories I can move this stuff to?

I wonder whether the time has come for arch/x86/virt/

xen/
kvm/
hyperv/
kernel/paravirt*
kernel/cpu/hypervisor.c

-boris

      parent reply	other threads:[~2017-12-08 19:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-07 22:45 Maran Wilson
2017-12-07 22:45 ` [RFC PATCH v2 1/2] xen/pvh: Add memory map pointer to hvm_start_info struct Maran Wilson
2017-12-08  8:49   ` Jan Beulich
2017-12-08 19:05     ` Maran Wilson
2017-12-11  9:25       ` Jan Beulich
2017-12-11 21:59     ` Paolo Bonzini
2017-12-12  8:06       ` Jan Beulich
2017-12-12  9:54         ` Paolo Bonzini
2017-12-07 22:45 ` [RFC PATCH v2 2/2] KVM: x86: Allow Qemu/KVM to use PVH entry point Maran Wilson
2017-12-08 19:21 ` Boris Ostrovsky [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=a506ad26-5e33-d99d-64a8-cefc3fa42c87@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=hch@infradead.org \
    --cc=hpa@zytor.com \
    --cc=jgross@suse.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maran.wilson@oracle.com \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=roger.pau@citrix.com \
    --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

all inboxes | Powered by JetHome®