From: Avi Kivity <avi@qumranet.com>
To: Carsten Otte <cotte@de.ibm.com>
Cc: sfr@canb.auug.org.au,
"kvm-devel@lists.sourceforge.net"
<kvm-devel@lists.sourceforge.net>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Olaf Schnapper <os@de.ibm.com>
Subject: Re: [PATCH 00/04] kvm-s390 updates
Date: Sat, 05 Apr 2008 00:11:26 +0300 [thread overview]
Message-ID: <47F6997E.2040104@qumranet.com> (raw)
In-Reply-To: <1207314746.18908.17.camel@cotte.boeblingen.de.ibm.com>
Carsten Otte wrote:
> Hi Avi,
>
> looks like Heiko played around with kvm a bit :-):
> 01/04: cosmetics, including part of Arnd's review feedback
> 02/04: bugfix, if KVM_VCPU_IOCTL_RUN got interrupted by signal
> 03/04: performance improvement with our pgste memory handling
> 04/04: resolve merge conflict in linux-next kvm.git versus git-s390
> that was reported by Stephen Rothwell today (thanks, Stephen!)
>
> I think it's save to queue all for 2.6.26, #2 and #4 seem crucial to me.
>
>
I applied 1, 2, and 4 (3 is broken). Will fold into the other s390
patches before submitting upstream.
--
Any sufficiently difficult bug is indistinguishable from a feature.
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
prev parent reply other threads:[~2008-04-04 21:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 13:12 [PATCH 00/04] kvm-s390 updates Carsten Otte
2008-04-04 14:03 ` [PATCH 03/04 v2] kvm-s390: Improve pgste accesses Carsten Otte
2008-04-04 21:12 ` Avi Kivity
2008-04-04 21:11 ` Avi Kivity [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=47F6997E.2040104@qumranet.com \
--to=avi@qumranet.com \
--cc=borntraeger@de.ibm.com \
--cc=cotte@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=os@de.ibm.com \
--cc=schwidefsky@de.ibm.com \
--cc=sfr@canb.auug.org.au \
/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.