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

Hi, 

> diff -r 5a7e18e57c72 -r 228f7aebb0ff xen/arch/x86/mm/mem_event.c
> --- a/xen/arch/x86/mm/mem_event.c
> +++ b/xen/arch/x86/mm/mem_event.c
> @@ -563,8 +563,11 @@ int mem_event_domctl(struct domain *d, x
>              if ( !hap_enabled(d) )
>                  break;
> 
> -            /* Currently only EPT is supported */
> -            if ( boot_cpu_data.x86_vendor != X86_VENDOR_INTEL )
> +            /* Currently EPT or AMD with no iommu/hap page table sharing are
> +             * supported. Further, AMD considered experimental atm. */
> +            if ( !((boot_cpu_data.x86_vendor == X86_VENDOR_INTEL) ||
> +                   ((boot_cpu_data.x86_vendor == X86_VENDOR_AMD) &&
> +                     !iommu_use_hap_pt(d))) )

I think we can just drop the test for Intelness rather than adding one
for AMDness.  hap_enabled() above is good enough to avoid Cyrix &c. :)
Also, I think the cset I just checked in to interlock IOMMU vs
sharing/paging should be enough that we don't need the
!iommu_use_hap_pt(d) test either (or is there some concern about the 
pagetable layout?) 

That is, can we just drop this whole test?

The right place to mark it experimental is in the user docs and example
config files. 

Cheers,

Tim.

  reply	other threads:[~2012-03-29 15:42 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 [this message]
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
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=20120329154243.GI72859@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).