xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Juergen Gross <JGross@suse.com>, Peng Fan <peng.fan@nxp.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	George Dunlap <george.dunlap@eu.citrix.com>,
	AndrewCooper <andrew.cooper3@citrix.com>,
	Xen Devel <xen-devel@lists.xen.org>,
	anastassios.nanos@onapp.com, Peng Fan <van.freenix@gmail.com>
Subject: Re: [DOC RFC] Heterogeneous Multi Processing Support in Xen
Date: Thu, 8 Dec 2016 11:23:58 +0100	[thread overview]
Message-ID: <1481192638.3445.152.camel@citrix.com> (raw)
In-Reply-To: <584940B00200007800126A04@prv-mh.provo.novell.com>


[-- Attachment #1.1: Type: text/plain, Size: 1108 bytes --]

On Thu, 2016-12-08 at 03:14 -0700, Jan Beulich wrote:
> > > > On 07.12.16 at 19:29, <dario.faggioli@citrix.com> wrote:
> > ### x86
> > 
> > There is no HMP platform of relevance, for now, in x86 world.
> > Therefore,
> > only one class will exist, and all the CPUs will be set to belong
> > to it.
> > **TODO X86:** is this correct?
> 
> What about the original Xeon Phi (on a PCIe card)?
> 
Well, what I'd say about it is that I did not know about its existence.
:-)

Anyway, if we have HMP on x86 already, and we want to support them,
we'll have to define criteria for building classes there too. Once that
is done, the rest of this document should be general enough (or at
least that was the intent).

About defining those criteria, I'd appreciate whatever input you x86
experts will be able to share. :-)

Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

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

  reply	other threads:[~2016-12-08 10:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-07 18:29 [DOC RFC] Heterogeneous Multi Processing Support in Xen Dario Faggioli
2016-12-08  6:12 ` Juergen Gross
2016-12-08 10:27   ` Dario Faggioli
2016-12-08 10:38     ` Juergen Gross
2016-12-08 21:45       ` Dario Faggioli
2016-12-15 18:41       ` Dario Faggioli
2016-12-16  7:44         ` Juergen Gross
2016-12-08 10:14 ` Jan Beulich
2016-12-08 10:23   ` Dario Faggioli [this message]
2016-12-08 10:41     ` Jan Beulich
2016-12-08 19:09   ` Stefano Stabellini
2016-12-08 21:54   ` Dario Faggioli
2016-12-09  8:13     ` Jan Beulich
2016-12-09  8:29       ` Dario Faggioli
2016-12-09  9:09         ` Jan Beulich
2016-12-09 19:20           ` Stefano Stabellini
2016-12-16  8:00           ` George Dunlap
2016-12-16  8:05 ` George Dunlap
2016-12-16  8:07   ` George Dunlap
2017-03-01  0:05 ` Anastassios Nanos
2017-03-01 17:38   ` Dario Faggioli
2017-03-01 18:58     ` Stefano Stabellini

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=1481192638.3445.152.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=JGross@suse.com \
    --cc=anastassios.nanos@onapp.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=peng.fan@nxp.com \
    --cc=sstabellini@kernel.org \
    --cc=van.freenix@gmail.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).