From: Will Deacon <will.deacon@arm.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Andre Przywara <andre.przywara@arm.com>,
Aneesh Kumar <aneesh.kumar@linux.vnet.ibm.com>,
Sasha Levin <sasha.levin@oracle.com>,
Pekka Enberg <penberg@kernel.org>,
kvm@vger.kernel.org
Subject: Re: [PATCH 0/3] kvmtool: don't overwrite /virt/init
Date: Tue, 27 Oct 2015 17:06:35 +0000 [thread overview]
Message-ID: <20151027170635.GA22049@arm.com> (raw)
In-Reply-To: <20151022155921.GA15527@redhat.com>
Hi Oleg,
On Thu, Oct 22, 2015 at 05:59:21PM +0200, Oleg Nesterov wrote:
> On top of "[PATCH 0/3] kvmtool: tiny init fox x86_64" I sent.
>
> I simply can't understand why kvmtool always overwrites /virt/init.
> This doesn't look right, especially because you can't pass "init="
> kernel argument without another patch "[PATCH] kvmtool/run: append
> cfg.kernel_cmdline at the end of real_cmdline" I sent. And so far
> it is not clear to me if you are going to accept that patch or not.
Sorry, I was off last week and didn't have email access. I'm going through
my inbox now and your patches look pretty good to me. I'll apply/test and
then push out if I don't see any issues.
Thanks!
Will
prev parent reply other threads:[~2015-10-27 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 15:59 [PATCH 0/3] kvmtool: don't overwrite /virt/init Oleg Nesterov
2015-10-22 15:59 ` [PATCH 1/3] kvmtool: add lkvm-static to gitignore Oleg Nesterov
2015-10-22 15:59 ` [PATCH 2/3] kvmtool/run: don't abuse "root=" parameter, don't pass "rw" to v9fs_mount() Oleg Nesterov
2015-10-22 15:59 ` [PATCH 3/3] kvmtool/run: do not overwrite /virt/init Oleg Nesterov
2015-10-27 17:06 ` Will Deacon [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=20151027170635.GA22049@arm.com \
--to=will.deacon@arm.com \
--cc=andre.przywara@arm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=penberg@kernel.org \
--cc=sasha.levin@oracle.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).