From: Gleb Natapov <gleb@redhat.com>
To: Chris Metcalf <cmetcalf@tilera.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>,
Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH v2] tile: support KVM for tilegx
Date: Tue, 3 Sep 2013 20:39:31 +0300 [thread overview]
Message-ID: <20130903173931.GO10142@redhat.com> (raw)
In-Reply-To: <52261D26.7060206@tilera.com>
On Tue, Sep 03, 2013 at 01:32:22PM -0400, Chris Metcalf wrote:
> On 8/26/2013 8:04 AM, Gleb Natapov wrote:
> > On Sun, Aug 25, 2013 at 09:26:47PM -0400, Chris Metcalf wrote:
> >> On 8/25/2013 7:39 AM, Gleb Natapov wrote:
> >>> On Mon, Aug 12, 2013 at 04:24:11PM -0400, Chris Metcalf wrote:
> >>>> This change provides the initial framework support for KVM on tilegx.
> >>>> Basic virtual disk and networking is supported.
> >>>>
> >>> This needs to be broken down to more reviewable patches.
>
> Ping! I'd like to ask Linus to pull the tile tree now that 3.12 is open.
> Let me know if this would be problematic for you.
>
That was sent to close to merge window and I and Paolo had vocations in
August so with the email backlog we had no time to review it. Lets wait
for 2.13 and I will give its review top priority after the merge
windows.
> I think the tile KVM bits are in good enough shape that it makes sense
> to pull them, and if there are follow-up concerns they can be addressed
> later in the 3.12-rc series, or in future kernel releases.
>
> In particular, it's probably worth noting the one generic change in the
> series, which is adding a KVM_EXIT_AGAIN value. If this seems like it
> might be problematic, I can pull it for now and leave it for later review;
> it's basically just a performance optimization.
>
> The v3 series is at:
>
> https://lkml.org/lkml/2013/8/28/675
> https://lkml.org/lkml/2013/8/28/672
> https://lkml.org/lkml/2013/8/28/676
>
> Thank you!
>
> --
> Chris Metcalf, Tilera Corp.
> http://www.tilera.com
--
Gleb.
next prev parent reply other threads:[~2013-09-03 17:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 15:24 [PATCH] tile: support KVM for tilegx Chris Metcalf
2013-08-12 17:08 ` Jan Kiszka
2013-08-12 20:24 ` [PATCH v2] " Chris Metcalf
2013-08-25 11:39 ` Gleb Natapov
2013-08-26 1:26 ` Chris Metcalf
2013-08-26 12:04 ` Gleb Natapov
2013-08-28 19:45 ` [PATCH v3 1/3] tile: support KVM host mode Chris Metcalf
2013-09-10 10:53 ` Gleb Natapov
2013-09-10 11:59 ` Paolo Bonzini
2013-09-30 20:11 ` Chris Metcalf
2013-10-01 15:21 ` Gleb Natapov
2013-08-28 20:57 ` [PATCH v3 2/3] tile: enable building as a paravirtualized KVM_GUEST Chris Metcalf
2013-08-28 20:58 ` [PATCH v3 3/3] tile: enable VIRTIO support for KVM Chris Metcalf
2013-09-10 12:47 ` Paolo Bonzini
2013-09-30 20:11 ` Chris Metcalf
2013-10-01 6:39 ` Paolo Bonzini
2013-08-29 0:26 ` [PATCH v2] tile: support KVM for tilegx Chris Metcalf
2013-09-03 17:32 ` Chris Metcalf
2013-09-03 17:39 ` Gleb Natapov [this message]
2013-09-03 17:46 ` Chris Metcalf
2013-09-03 18:13 ` [PATCH 1/3] tile: clean up relocate_kernel_64 debug code Chris Metcalf
2013-09-03 18:41 ` [PATCH 3/3] tile: parameterize VA and PA space more cleanly Chris Metcalf
2013-09-03 18:45 ` [PATCH 2/3] tile: don't assume user privilege is zero Chris Metcalf
2013-09-03 19:09 ` [PATCH 0/3] tile prerequisites for KVM support Chris Metcalf
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=20130903173931.GO10142@redhat.com \
--to=gleb@redhat.com \
--cc=cmetcalf@tilera.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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).