All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jinpu Wang <jinpu.wang@ionos.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Yang Zhong <yang.zhong@intel.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	qemu-devel@nongnu.org, Yu Zhang <yu.zhang@ionos.com>
Subject: Re: RFC: sgx-epc is not listed in machine type help
Date: Thu, 28 Apr 2022 14:57:51 +0200	[thread overview]
Message-ID: <CAMGffEm-9+p7cRqfpzGYY_qNE1Fgqo5f4Qg9CTHdRz9ziGzH+w@mail.gmail.com> (raw)
In-Reply-To: <YmqJfa9510SO1yuS@redhat.com>

Hi Daniel,

On Thu, Apr 28, 2022 at 2:33 PM Daniel P. Berrangé <berrange@redhat.com> wrote:
>
> On Thu, Apr 28, 2022 at 02:18:54PM +0200, Jinpu Wang wrote:
> > On Thu, Apr 28, 2022 at 2:05 PM Yang Zhong <yang.zhong@intel.com> wrote:
> > >
> > > On Thu, Apr 28, 2022 at 01:59:33PM +0200, Jinpu Wang wrote:
> > > > Hi Yang, hi Paolo,
> > > >
> > > > We noticed sgx-epc machine type is not listed in the output of
> > > > "qemu-system-x86_64 -M ?",
> > snip
> > > >
> > > >
> > > > I think this would cause confusion to users, is there a reason behind this?
> > > >
> > >
> > >   No specific machine type for SGX, and SGX is only supported in Qemu PC and Q35 platform.
> > Hi Yang,
> >
> > Thanks for your quick reply. Sorry for the stupid question.
> > The information I've got from intel or the help sample from
> > https://www.qemu.org/docs/master/system/i386/sgx.html, We need to
> > specify commands something like this to run SGX-EPC guest:
> > qemu-system-x86-64 -m 2G -nographic -enable-kvm -cpu
> > host,+sgx-provisionkey  -object
> > memory-backend-epc,id=mem1,size=512M,prealloc=on -M
> > sgx-epc.0.memdev=mem1,sgx-epc.0.node=0 /tmp/volume-name.img
>
> That isn't an sgx-epc machine type.
>
> That is an (implicit) i440fx  machine type, with an sgx-epc.0.memdev
> property being set.
>
>
> With regards,
> Daniel
Thanks for your reply, I have better understanding now.
> --
> |: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
> |: https://libvirt.org         -o-            https://fstop138.berrange.com :|
> |: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|
>


      reply	other threads:[~2022-04-28 13:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28 11:59 RFC: sgx-epc is not listed in machine type help Jinpu Wang
2022-04-28 11:48 ` Yang Zhong
2022-04-28 12:18   ` Jinpu Wang
2022-04-28 12:16     ` Yang Zhong
2022-04-28 12:56       ` Jinpu Wang
2022-04-29  2:05         ` Yang Zhong
2022-04-29  4:11           ` Jinpu Wang
2022-04-28 12:33     ` Daniel P. Berrangé
2022-04-28 12:57       ` Jinpu Wang [this message]

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=CAMGffEm-9+p7cRqfpzGYY_qNE1Fgqo5f4Qg9CTHdRz9ziGzH+w@mail.gmail.com \
    --to=jinpu.wang@ionos.com \
    --cc=berrange@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yang.zhong@intel.com \
    --cc=yu.zhang@ionos.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.