All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: Kevin Tian <kevin.tian@intel.com>,
	Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
	Jun Nakajima <jun.nakajima@intel.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Eddie Dong <eddie.dong@intel.com>,
	Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>,
	Jan Beulich <jbeulich@suse.com>,
	xen-devel@lists.xenproject.org,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH v2 11/22] xen/x86: allow disabling emulated devices for HVM guests
Date: Fri, 10 Jul 2015 14:54:11 -0400	[thread overview]
Message-ID: <20150710185411.GC30788@l.oracle.com> (raw)
In-Reply-To: <5594FEFD.2090603@citrix.com>

> Also, from a guest POV, how is the hw emulated local apic going to be
> used? Are we going to route the interrupts from virtual devices
> (netfront, blkfront) to the lapic? Or we just want it for the timer and
> ditch the PV timer?

Use the event channels for the PV. For PCIe devices (passthrough)
use the APIC.

> 
> I can see that this is more interesting for a PVH/HVMlite Dom0, but
> still in that case I'm not sure how a guest is supposed to interact with
> it. Will the PHYSDEV hypercalls route interrupts to the emulated local
> apic instead of pirqs event channels? Will we trap PCI/MSI/MSI-X
> configuration and emulate it?

The thought I had was that with VT-D posted interrupts would
do the heavy lifting. And when the interrupts do get to us and
have to vmexit - well we would do the normal HVM path for those
that are interested.

And for those that want the event callback vector - we can still
do that. I hadn't thought much of details on this yet -perhaps
this should be discussed next Developer summit to hash some of
this out.

  reply	other threads:[~2015-07-10 18:54 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-01 14:45 [PATCH v2 00/22] Introduce HVM without dm and new boot ABI Roger Pau Monne
2015-07-01 14:45 ` [PATCH v2 01/22] libxc: split x86 HVM setup_guest into smaller logical functions Roger Pau Monne
2015-07-01 14:45 ` [PATCH v2 02/22] libxc: unify xc_dom_p2m_{host/guest} Roger Pau Monne
2015-07-01 14:45 ` [PATCH v2 03/22] libxc: introduce the notion of a container type Roger Pau Monne
2015-07-01 14:45 ` [PATCH v2 04/22] libxc: introduce a domain loader for HVM guest firmware Roger Pau Monne
2015-07-01 14:45 ` [PATCH v2 05/22] libxc: make arch_setup_meminit a xc_dom_arch hook Roger Pau Monne
2015-07-01 14:45 ` [PATCH v2 06/22] libxc: make arch_setup_boot{init/late} xc_dom_arch hooks Roger Pau Monne
2015-07-01 14:46 ` [PATCH v2 07/22] xen/x86: fix arch_set_info_guest for HVM guests Roger Pau Monne
2015-07-01 14:46 ` [PATCH v2 08/22] libxc: introduce a xc_dom_arch for hvm-3.0-x86_32 guests Roger Pau Monne
2015-07-01 14:46 ` [PATCH v2 09/22] libxl: switch HVM domain building to use xc_dom_* helpers Roger Pau Monne
2015-07-01 14:46 ` [PATCH v2 10/22] libxc: remove dead HVM building code Roger Pau Monne
2015-07-01 14:46 ` [PATCH v2 11/22] xen/x86: allow disabling emulated devices for HVM guests Roger Pau Monne
2015-07-01 15:25   ` Paul Durrant
2015-07-01 15:34     ` Roger Pau Monné
2015-07-01 15:39       ` Paul Durrant
2015-07-01 15:46   ` Andrew Cooper
2015-07-01 15:51     ` Boris Ostrovsky
2015-07-01 16:01       ` Andrew Cooper
2015-07-01 16:13         ` Stefano Stabellini
2015-07-01 16:48           ` Andrew Cooper
2015-07-02 11:49             ` Stefano Stabellini
2015-07-02 13:34               ` Boris Ostrovsky
2015-07-02  9:06     ` Roger Pau Monné
2015-07-10 18:54       ` Konrad Rzeszutek Wilk [this message]
2015-07-01 14:46 ` [PATCH v2 12/22] elfnotes: intorduce a new PHYS_ENTRY elfnote Roger Pau Monne
2015-07-03 10:36   ` David Vrabel
2015-07-03 10:52     ` Roger Pau Monné
2015-07-01 14:46 ` [PATCH v2 13/22] lib{xc/xl}: allow creating domains without emulated devices Roger Pau Monne
2015-07-01 14:46 ` [PATCH v2 14/22] xen: allow HVM guests to use XENMEM_memory_map Roger Pau Monne
2015-07-01 14:46 ` [PATCH v2 15/22] xen/x86: allow HVM guests to use hypercalls to bring up vCPUs Roger Pau Monne
2015-07-01 14:46 ` [PATCH v2 16/22] xenconsole: try to attach to PV console if HVM fails Roger Pau Monne
2015-07-01 14:46 ` [PATCH v2 17/22] libxc: change the position of the special pages Roger Pau Monne
2015-07-01 14:46 ` [PATCH v2 18/22] libxc/xen: introduce HVM_PARAM_CMDLINE_PFN Roger Pau Monne
2015-07-01 14:46 ` [PATCH v2 19/22] libxc/xen: introduce HVM_PARAM_FIRST_FREE_PFN Roger Pau Monne
2015-07-01 14:46 ` [PATCH v2 20/22] libxc/xen: introduce HVM_PARAM_MODLIST_PFN Roger Pau Monne
2015-07-01 14:46 ` [PATCH v2 21/22] libxl: set correct nic type for HVM guests without a device model Roger Pau Monne
2015-07-01 14:46 ` [PATCH v2 22/22] lib{xc/xl}: allow the creation of HVM domains with a kernel Roger Pau Monne
2015-07-03  1:59 ` [PATCH v2 00/22] Introduce HVM without dm and new boot ABI Yang Hongyang
2015-07-03  7:02   ` Roger Pau Monné

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=20150710185411.GC30788@l.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=Aravind.Gopalakrishnan@amd.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=eddie.dong@intel.com \
    --cc=jbeulich@suse.com \
    --cc=jun.nakajima@intel.com \
    --cc=kevin.tian@intel.com \
    --cc=roger.pau@citrix.com \
    --cc=suravee.suthikulpanit@amd.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.