qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: CheneyLin <linzc@zju.edu.cn>
To: qemu-devel@nongnu.org
Cc: aik@ozlabs.ru, pbonzini@redhat.com
Subject: [Qemu-devel]   question about share flatviews
Date: Sun, 14 Jan 2018 20:20:19 +0800 (GMT+08:00)	[thread overview]
Message-ID: <2f3d36f8.1ce36.160f49d0471.Coremail.linzc@zju.edu.cn> (raw)

Hi， Paolo,

Alexey
Alexey
Alexey
Alexey
Alexey
Alexey
Alexey
Alexey
Alexey
Alexey：

commit 967dc9b

commit 967dc9b
commit 967dc9b
commit 967dc9b Share FlatView's and dispatch trees between address spaces
 commit 967dc9b.
. 

I'm wondering why we have to shares flatviews between different ASes. In my opinion, arch like x86 only have two ASes(memory AS and io AS), each AS is related with only one flatview. Their ASes are definitely different.

             reply	other threads:[~2018-01-14 12:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-14 12:20 CheneyLin [this message]
2018-01-15  3:37 ` [Qemu-devel] question about share flatviews Alexey Kardashevskiy
2018-01-15  9:29 ` Paolo Bonzini

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=2f3d36f8.1ce36.160f49d0471.Coremail.linzc@zju.edu.cn \
    --to=linzc@zju.edu.cn \
    --cc=aik@ozlabs.ru \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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).