From: Pekka Enberg <penberg@iki.fi>
To: James Hogan <james.hogan@imgtec.com>,
Andreas Herrmann <andreas.herrmann@caviumnetworks.com>,
Pekka Enberg <penberg@kernel.org>
Cc: David Daney <ddaney.cavm@gmail.com>,
kvm@vger.kernel.org, linux-mips@linux-mips.org
Subject: Re: [PATCH v2 00/12] kvm tools: Misc patches (mips support)
Date: Tue, 20 May 2014 20:52:46 +0300 [thread overview]
Message-ID: <537B966E.9000708@iki.fi> (raw)
In-Reply-To: <537B3A8E.70801@imgtec.com>
On 05/20/2014 02:20 PM, James Hogan wrote:
> I don't know what Pekka's policy is for kvm tools, but to avoid
> confusion I'd like to make clear that this patchset depends on a KVM
> implementation (KVM_VM_TYPE==1 for VZ) which hasn't been accepted into
> the mainline kernel yet.
Is that something that is likely to end up in mainline Linux in one form
or another? If yes, we can merge early like we did with arm64.
- Pekka
next prev parent reply other threads:[~2014-05-20 17:52 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 16:53 [PATCH v2 00/12] kvm tools: Misc patches (mips support) Andreas Herrmann
2014-05-19 16:53 ` Andreas Herrmann
2014-05-19 16:53 ` [PATCH v2 01/12] kvm tools: Print message on failure of KVM_CREATE_VM Andreas Herrmann
2014-05-19 16:53 ` Andreas Herrmann
2014-05-19 16:53 ` [PATCH v2 02/12] kvm tools: Fix print format warnings Andreas Herrmann
2014-05-19 16:53 ` Andreas Herrmann
2014-05-19 16:53 ` [PATCH v2 03/12] kvm tools: Move definition of TERM_MAX_DEVS to header Andreas Herrmann
2014-05-19 16:53 ` Andreas Herrmann
2014-05-19 16:53 ` [PATCH v2 04/12] kvm tools: Allow to load ELF binary Andreas Herrmann
2014-05-19 16:53 ` Andreas Herrmann
2014-05-19 16:53 ` [PATCH v2 05/12] kvm tools: Introduce weak (default) load_bzimage function Andreas Herrmann
2014-05-19 16:53 ` Andreas Herrmann
2014-05-19 16:53 ` [PATCH v2 06/12] kvm tools, mips: Add MIPS support Andreas Herrmann
2014-05-19 16:53 ` Andreas Herrmann
2014-05-19 16:53 ` [PATCH v2 07/12] kvm tools, mips: Enable build of mips support Andreas Herrmann
2014-05-19 16:53 ` Andreas Herrmann
2014-05-19 16:53 ` [PATCH v2 08/12] kvm tools: Provide per arch macro to specify type for KVM_CREATE_VM Andreas Herrmann
2014-05-19 16:53 ` Andreas Herrmann
2014-05-20 11:24 ` James Hogan
2014-05-20 11:24 ` James Hogan
2014-05-20 14:55 ` Andreas Herrmann
2014-05-20 14:55 ` Andreas Herrmann
2014-05-19 16:53 ` [PATCH v2 09/12] kvm tools: Handle virtio/pci I/O space as little endian Andreas Herrmann
2014-05-19 16:53 ` Andreas Herrmann
2014-05-19 16:53 ` [PATCH v2 10/12] kvm tools, mips: Add support for loading elf binaries Andreas Herrmann
2014-05-19 16:53 ` Andreas Herrmann
2014-05-19 16:53 ` [PATCH v2 11/12] kvm tools: Modify term_putc to write more than one char Andreas Herrmann
2014-05-19 16:53 ` Andreas Herrmann
2014-05-19 16:53 ` [PATCH v2 12/12] kvm tools: Return number of bytes written by term_putc Andreas Herrmann
2014-05-19 16:53 ` Andreas Herrmann
2014-05-20 11:20 ` [PATCH v2 00/12] kvm tools: Misc patches (mips support) James Hogan
2014-05-20 11:20 ` James Hogan
2014-05-20 17:52 ` Pekka Enberg [this message]
2014-05-20 21:25 ` James Hogan
2014-05-20 21:25 ` James Hogan
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=537B966E.9000708@iki.fi \
--to=penberg@iki.fi \
--cc=andreas.herrmann@caviumnetworks.com \
--cc=ddaney.cavm@gmail.com \
--cc=james.hogan@imgtec.com \
--cc=kvm@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=penberg@kernel.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