qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé via" <qemu-devel@nongnu.org>
To: qemu-devel@nongnu.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Yang Zhong" <yang.zhong@intel.com>,
	"Eduardo Habkost" <eduardo@habkost.net>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: [PATCH 0/2] hw/i386: QOM-attach CPUs/SGX-EPC objects to their parents
Date: Mon, 17 Jan 2022 00:53:29 +0100	[thread overview]
Message-ID: <20220116235331.103977-1-f4bug@amsat.org> (raw)

Trying to fix the issue reported here:
https://lists.nongnu.org/archive/html/qemu-devel/2021-11/msg05670.html

First attach the CPUs to the machine,
then the SGX-EPC to its memory backend.

Philippe Mathieu-Daudé (2):
  hw/i386/x86: Attach CPUs to machine
  hw/i386/sgx: Attach SGX-EPC to its memory backend

 hw/i386/sgx.c | 3 +++
 hw/i386/x86.c | 1 +
 2 files changed, 4 insertions(+)

-- 
2.34.1



             reply	other threads:[~2022-01-16 23:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-16 23:53 Philippe Mathieu-Daudé via [this message]
2022-01-16 23:53 ` [PATCH 1/2] hw/i386/x86: Attach CPUs to machine Philippe Mathieu-Daudé via
2022-01-17 13:48   ` Daniel P. Berrangé
2022-01-17 14:57     ` Philippe Mathieu-Daudé via
2022-01-18  2:15     ` Yang Zhong
2022-01-16 23:53 ` [RFC PATCH 2/2] hw/i386/sgx: Attach SGX-EPC to its memory backend Philippe Mathieu-Daudé via
2022-01-17 11:48   ` Paolo Bonzini
2022-01-17 12:08     ` Philippe Mathieu-Daudé via
2022-01-18  2:33     ` Yang Zhong
2022-01-23 12:52     ` Yang Zhong
2022-01-31 23:41       ` Philippe Mathieu-Daudé via

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=20220116235331.103977-1-f4bug@amsat.org \
    --to=qemu-devel@nongnu.org \
    --cc=eduardo@habkost.net \
    --cc=f4bug@amsat.org \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=richard.henderson@linaro.org \
    --cc=yang.zhong@intel.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 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).