All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: FionaLi-oc <fionali-oc@zhaoxin.com>, xen-devel@lists.xenproject.org
Cc: cobechen@zhaoxin.com, wei.liu2@citrix.com, jbeulich@suse.com,
	roger.pau@citrix.com
Subject: Re: [PATCH 0/2] x86/iommu: support IOMMU for Zhaoxin CPU
Date: Tue, 9 Apr 2019 10:02:57 +0100	[thread overview]
Message-ID: <37f85edf-eff9-43bc-9ecc-674da62f1403@citrix.com> (raw)
In-Reply-To: <1554778767-3480-1-git-send-email-fionali-oc@zhaoxin.com>

On 09/04/2019 03:59, FionaLi-oc wrote:
> The patchset supports some features for Zhaoxin CPU whose vendor
> ID is 'Shanghai'. Zhaoxin x86 SOC supports I/O virtualization
> which is compatible with Intel I/O virtulizaiton.
>
> Indent with four spaces.
>
> Signed-off-by: FionaLi-oc <fionali-oc@zhaoxin.com>

Please would you test the staging branch of Xen.

Some very recent changes of Jan's for AMD x2apic support have included
http://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=1b3cc8000c82edc9761c1e595928d6584e11f9f5
which drops this clause, and should initialise VT-d based on the
presence of the DMAR table, rather than the exact CPU vendor.

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

WARNING: multiple messages have this Message-ID (diff)
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: FionaLi-oc <fionali-oc@zhaoxin.com>, <xen-devel@lists.xenproject.org>
Cc: cobechen@zhaoxin.com, wei.liu2@citrix.com, jbeulich@suse.com,
	roger.pau@citrix.com
Subject: Re: [Xen-devel] [PATCH 0/2] x86/iommu: support IOMMU for Zhaoxin CPU
Date: Tue, 9 Apr 2019 10:02:57 +0100	[thread overview]
Message-ID: <37f85edf-eff9-43bc-9ecc-674da62f1403@citrix.com> (raw)
Message-ID: <20190409090257.rzX6h_0nEvy17FOLGmuEDIBMNG1FVEWQELEmRhsBLEE@z> (raw)
In-Reply-To: <1554778767-3480-1-git-send-email-fionali-oc@zhaoxin.com>

On 09/04/2019 03:59, FionaLi-oc wrote:
> The patchset supports some features for Zhaoxin CPU whose vendor
> ID is 'Shanghai'. Zhaoxin x86 SOC supports I/O virtualization
> which is compatible with Intel I/O virtulizaiton.
>
> Indent with four spaces.
>
> Signed-off-by: FionaLi-oc <fionali-oc@zhaoxin.com>

Please would you test the staging branch of Xen.

Some very recent changes of Jan's for AMD x2apic support have included
http://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=1b3cc8000c82edc9761c1e595928d6584e11f9f5
which drops this clause, and should initialise VT-d based on the
presence of the DMAR table, rather than the exact CPU vendor.

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2019-04-09  9:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09  2:59 [PATCH 0/2] x86/iommu: support IOMMU for Zhaoxin CPU FionaLi-oc
2019-04-09  2:59 ` [Xen-devel] " FionaLi-oc
2019-04-09  9:02 ` Andrew Cooper [this message]
2019-04-09  9:02   ` Andrew Cooper

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=37f85edf-eff9-43bc-9ecc-674da62f1403@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=cobechen@zhaoxin.com \
    --cc=fionali-oc@zhaoxin.com \
    --cc=jbeulich@suse.com \
    --cc=roger.pau@citrix.com \
    --cc=wei.liu2@citrix.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.