xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Tim Deegan <tim@xen.org>
To: Olaf Hering <olaf@aepfle.de>
Cc: keir@xen.org, andres@gridcentric.ca, xen-devel@lists.xen.org,
	wei.wang2@amd.com, Andres Lagar-Cavilla <andres@lagarcavilla.org>,
	jbeulich@suse.com, adin@gridcentric.ca
Subject: Re: [PATCH 0 of 2] Support for Paging/Sharing on AMD
Date: Thu, 29 Mar 2012 17:58:36 +0100	[thread overview]
Message-ID: <20120329165836.GL72859@ocelot.phlegethon.org> (raw)
In-Reply-To: <20120329164123.GA10693@aepfle.de>

At 18:41 +0200 on 29 Mar (1333046483), Olaf Hering wrote:
> On Thu, Mar 29, Tim Deegan wrote:
> 
> > At 18:01 +0200 on 29 Mar (1333044093), Olaf Hering wrote:
> > > On Thu, Mar 29, Tim Deegan wrote:
> > > 
> > > > That is, can we just drop this whole test?
> > > 
> > > I'm ok with removing the existing boot_cpu_data.x86_vendor test,
> > > check only hap_enabled() and return -ENODEV otherwise.
> > > 
> > > A recent change added need_iommu() check, this should be moved up into
> > > the -ENODEV case becasue -EXDEV is for PoD.
> > 
> > That seems strange -- why would 'no; this VM uses PoD' be different from
> > 'no; this VM uses the IOMMU'?
> 
> Its just a made-up return code to have a proper error message in
> xenpagings init function.

Uh, OK.  But when we're adding this iommu interlock, it seems better to
bundle it in with PoD as 'VM is using an incompatible feature'.

> > I'll take a patch to change the return code if it also documents it in
> > the hypercall interface. :)
> 
> Where is it documented?

In the public headers (but basically not documented at all, even there).
There is some markup language (see, e.g. public/xen.h) that is used to
generate separate documentation, but public/domctl.h doesn't seem to
have any of that yet.

Tim.

  reply	other threads:[~2012-03-29 16:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-27 15:43 [PATCH 0 of 2] Support for Paging/Sharing on AMD Andres Lagar-Cavilla
2012-03-27 15:43 ` [PATCH 1 of 2] x86/mm: Teach paging to page table-based p2m Andres Lagar-Cavilla
2012-03-27 15:43 ` [PATCH 2 of 2] x86/mm: Make iommu passthrough and mem paging/sharing mutually exclusive Andres Lagar-Cavilla
2012-03-29 11:03 ` [PATCH 0 of 2] Support for Paging/Sharing on AMD Tim Deegan
2012-03-29 14:46   ` Andres Lagar-Cavilla
2012-03-29 15:01     ` Tim Deegan
2012-03-29 15:26       ` Andres Lagar-Cavilla
2012-03-29 15:42         ` Tim Deegan
2012-03-29 15:48           ` Andres Lagar-Cavilla
2012-03-29 16:00             ` Tim Deegan
2012-03-29 16:01           ` Olaf Hering
2012-03-29 16:05             ` Andres Lagar-Cavilla
2012-03-29 16:08             ` Tim Deegan
2012-03-29 16:41               ` Olaf Hering
2012-03-29 16:58                 ` Tim Deegan [this message]
2012-04-03 14:42     ` Olaf Hering
2012-04-03 15:10       ` Andres Lagar-Cavilla
2012-04-03 15:16         ` Olaf Hering

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=20120329165836.GL72859@ocelot.phlegethon.org \
    --to=tim@xen.org \
    --cc=adin@gridcentric.ca \
    --cc=andres@gridcentric.ca \
    --cc=andres@lagarcavilla.org \
    --cc=jbeulich@suse.com \
    --cc=keir@xen.org \
    --cc=olaf@aepfle.de \
    --cc=wei.wang2@amd.com \
    --cc=xen-devel@lists.xen.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).