From: Christian Ehrhardt <ehrhardt-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: Hollis Blanchard
<hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>,
kvm-ppc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 0 of 5] PowerPC patches for 2.6.27
Date: Tue, 29 Jul 2008 09:20:16 +0200 [thread overview]
Message-ID: <200807290920.17035.ehrhardt@linux.vnet.ibm.com> (raw)
In-Reply-To: <488C36DE.70507-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
On Sunday 27 July 2008 10:50:38 Avi Kivity wrote:
> Hollis Blanchard wrote:
> > Hi Avi, can these patches go upstream for 2.6.27? There's a bug fix,
> > the addition of hardware breakpoint functionality, and three very
> > significant performance improvements.
> >
> > By the way, I will be on vacation for a few weeks starting Monday, but
> > Christian Ehrhardt should be able to take care of any technical issues.
>
> Applied all; thanks. I prefer to only merge bug fixes at this time for
> 2.6.27. As far as I can tell, patch 2 is independent of the rest so
> I'll queue that. Let me know if that works.
Yes these patches are independent - for the type question you can consider
1/5 - feature
2/5 - bug fix
3,4,5/5 - yeah what is it .. neither a pure bug fix nor a feature let's call
it "performance fix"
We tested most of those performance fixes at least 1.5 Months now, having them
applied while developing new things on top and I feel very good with 3&4.
It would be nice if at least the performance fixes 3&4 could go in now under
the bug fix label too, but it's up to you.
--
Grüsse / regards,
Christian Ehrhardt
IBM Linux Technology Center, Open Virtualization
--
To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-07-29 7:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 18:54 [PATCH 0 of 5] PowerPC patches for 2.6.27 Hollis Blanchard
[not found] ` <patchbomb.1217012088-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-07-25 18:54 ` [PATCH 1 of 5] kvm: ppc: guest breakpoint support Hollis Blanchard
2008-07-25 18:54 ` [PATCH 2 of 5] kvm: ppc: fix invalidation of large guest pages Hollis Blanchard
2008-07-25 18:54 ` [PATCH 3 of 5] kvm: ppc: Stop saving host TLB state Hollis Blanchard
2008-07-25 18:54 ` [PATCH 4 of 5] kvm: ppc: Write only modified shadow entries into the TLB on exit Hollis Blanchard
2008-07-25 18:54 ` [PATCH 5 of 5] kvm: powerpc: Map guest userspace with TID=0 mappings Hollis Blanchard
[not found] ` <080b9c9515a5593babc8.1217012093-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-07-28 10:33 ` Liu Yu
2008-07-29 7:03 ` Christian Ehrhardt
2008-07-29 7:48 ` Liu Yu
2008-07-29 10:56 ` Liu Yu
2008-07-27 8:50 ` [PATCH 0 of 5] PowerPC patches for 2.6.27 Avi Kivity
[not found] ` <488C36DE.70507-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-07-29 7:20 ` Christian Ehrhardt [this message]
2008-07-29 13:00 ` Avi Kivity
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=200807290920.17035.ehrhardt@linux.vnet.ibm.com \
--to=ehrhardt-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=kvm-ppc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.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