All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Durrant <paul.durrant@citrix.com>
To: Sheng Yang <sheng@linux.intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: [PATCH][v2] Hybrid extension support in Xen
Date: Tue, 2 Feb 2010 11:32:23 +0000	[thread overview]
Message-ID: <4B680D47.3090707@citrix.com> (raw)
In-Reply-To: <201002021616.19189.sheng@linux.intel.com>

Sheng Yang wrote:
> 
> 1. Enable SMP support through VCPU_OP in arch_set_info_guest().
> 2. A new hypercall in hvm_ops to enable hybrid.
> 3. Mapping IRQ to VIRQ when deliver to the guest.
> 4. Inject a guest defined vector to deliver notification for events.
> 5. Use CPUID leaf 0x40000002 to support hybrid feature
> 6. Reserve some space at the end of MMIO hole for grant table use.
> 
> Please review. Thanks!
> 

Why a complete new hypercall table; could you not just use the existing 
HVM table and add the extra hypercalls in?
Doing it this way would negate the need for the concept of a 'hybrid' 
HVM guest would it not? HVM guests that were aware of the hybrid 
extensions would use them, those that were unaware would not.

Also, why the extra E820 space for the grant table? You don't need the 
table that early so could you not just use fake PCI BAR space or 
somesuch and do the XENMEM_add_to_physmap hypercall to add 
XENMAPSPACE_grant_table later on?

   Paul

-- 
===============================
Paul Durrant, Software Engineer

Citrix Systems (R&D) Ltd.
First Floor, Building 101
Cambridge Science Park
Milton Road
Cambridge CB4 0FY
United Kingdom
===============================

  parent reply	other threads:[~2010-02-02 11:32 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-02  8:16 [PATCH][v2] Hybrid extension support in Xen Sheng Yang
2010-02-02 11:22 ` Ian Campbell
2010-02-02 12:54   ` Sheng Yang
2010-02-02 13:19     ` Ian Campbell
2010-02-02 13:28       ` Sheng Yang
2010-02-02 13:50         ` Ian Campbell
2010-02-02 14:00           ` Tim Deegan
2010-02-02 14:22             ` Sheng Yang
2010-02-02 14:28           ` Sheng Yang
2010-02-02 13:35   ` Keir Fraser
2010-02-02 13:52     ` Sheng Yang
2010-02-02 14:01       ` Keir Fraser
2010-02-02 14:13         ` Sheng Yang
2010-02-02 11:26 ` Ian Campbell
2010-02-02 13:06   ` Sheng Yang
2010-02-02 13:52     ` Ian Campbell
2010-02-02 14:04       ` Stefano Stabellini
2010-02-02 14:07       ` Sheng Yang
2010-02-02 16:15         ` Ian Campbell
2010-02-02 16:31           ` Sheng Yang
2010-02-02 18:03             ` Ian Campbell
2010-02-02 18:27             ` Stefano Stabellini
2010-02-03  5:15               ` Sheng Yang
2010-02-03 10:39                 ` Tim Deegan
2010-02-02 11:32 ` Paul Durrant [this message]
2010-02-02 13:23 ` Keir Fraser
2010-02-02 13:37   ` Sheng Yang
2010-02-02 14:03     ` Keir Fraser
2010-02-02 14:08       ` Sheng Yang
2010-02-02 14:32         ` Keir Fraser
2010-02-02 14:37           ` Keir Fraser
2010-02-02 15:51             ` Sheng Yang
2010-02-02 14:39           ` Sheng Yang
2010-02-02 13:52 ` Ian Campbell
2010-02-02 13:53   ` Sheng Yang

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=4B680D47.3090707@citrix.com \
    --to=paul.durrant@citrix.com \
    --cc=Keir.Fraser@eu.citrix.com \
    --cc=sheng@linux.intel.com \
    --cc=xen-devel@lists.xensource.com \
    /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.