From: Sasha Levin <levinsasha928@gmail.com>
To: Zang Hongyong <zanghongyong@huawei.com>
Cc: wusongwei@huawei.com, kvm@vger.kernel.org, mst@redhat.com,
netdev@vger.kernel.org, hanweidong@huawei.com,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
xiaowei.yang@huawei.com
Subject: Re: [PATCH 0/2] vhot-net: Use kvm_memslots instead of vhost_memory to translate GPA to HVA
Date: Fri, 16 Dec 2011 10:07:28 +0200 [thread overview]
Message-ID: <1324022848.4496.27.camel@lappy> (raw)
In-Reply-To: <1324022358.4496.25.camel@lappy>
On Fri, 2011-12-16 at 09:59 +0200, Sasha Levin wrote:
> There has been a great deal of effort to keep vhost and kvm untangled.
> One example is the memory translation it has to do, another one is the
> eventfd/irqfd thing it does just so it could signal an IRQ in the guest
> instead of accessing the guest directly.
Actually, CONFIG_VHOST_NET doesn't even depend on CONFIG_KVM, so your
patch will break build when (CONFIG_VHOST_NET=y && CONFIG_KVM=n).
--
Sasha.
WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <levinsasha928@gmail.com>
To: Zang Hongyong <zanghongyong@huawei.com>
Cc: linux-kernel@vger.kernel.org, mst@redhat.com,
kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, xiaowei.yang@huawei.com,
hanweidong@huawei.com, wusongwei@huawei.com
Subject: Re: [PATCH 0/2] vhot-net: Use kvm_memslots instead of vhost_memory to translate GPA to HVA
Date: Fri, 16 Dec 2011 10:07:28 +0200 [thread overview]
Message-ID: <1324022848.4496.27.camel@lappy> (raw)
In-Reply-To: <1324022358.4496.25.camel@lappy>
On Fri, 2011-12-16 at 09:59 +0200, Sasha Levin wrote:
> There has been a great deal of effort to keep vhost and kvm untangled.
> One example is the memory translation it has to do, another one is the
> eventfd/irqfd thing it does just so it could signal an IRQ in the guest
> instead of accessing the guest directly.
Actually, CONFIG_VHOST_NET doesn't even depend on CONFIG_KVM, so your
patch will break build when (CONFIG_VHOST_NET=y && CONFIG_KVM=n).
--
Sasha.
next prev parent reply other threads:[~2011-12-16 8:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 5:32 [PATCH 0/2] vhot-net: Use kvm_memslots instead of vhost_memory to translate GPA to HVA zanghongyong
2011-12-16 5:32 ` [PATCH 1/2] kvm: Introduce get_kvm_from_task zanghongyong
2011-12-16 5:32 ` zanghongyong
2011-12-16 5:32 ` [PATCH 2/2] vhost-net: Use kvm_memslots for address translation zanghongyong
2011-12-16 5:32 ` zanghongyong
2011-12-16 7:05 ` [PATCH 0/2] vhot-net: Use kvm_memslots instead of vhost_memory to translate GPA to HVA Takuya Yoshikawa
2011-12-16 7:05 ` Takuya Yoshikawa
2011-12-16 7:05 ` Sasha Levin
2011-12-16 7:05 ` Sasha Levin
2011-12-16 7:40 ` Zang Hongyong
2011-12-16 7:59 ` Sasha Levin
2011-12-16 7:59 ` Sasha Levin
2011-12-16 8:07 ` Sasha Levin [this message]
2011-12-16 8:07 ` Sasha Levin
2011-12-16 8:18 ` Zang Hongyong
2011-12-16 8:18 ` Zang Hongyong
2011-12-16 7:40 ` Zang Hongyong
-- strict thread matches above, loose matches on Subject: below --
2011-12-16 5:32 zanghongyong
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=1324022848.4496.27.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=hanweidong@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=wusongwei@huawei.com \
--cc=xiaowei.yang@huawei.com \
--cc=zanghongyong@huawei.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.