From: Keir Fraser <keir@xen.org>
To: Jan Beulich <JBeulich@suse.com>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] miscellaneous cleanup
Date: Wed, 16 Jan 2013 15:46:25 +0000 [thread overview]
Message-ID: <CD1C7BD1.58B6E%keir@xen.org> (raw)
In-Reply-To: <50F6D7D902000078000B665C@nat28.tlf.novell.com>
On 16/01/2013 15:39, "Jan Beulich" <JBeulich@suse.com> wrote:
> ... noticed while putting together the 16Tb support patches for x86.
>
> Briefly, this (in order of the changes below)
> - fixes an inefficiency in x86's context switch code (translations to/
> from struct page are more involved than to/from MFNs)
> - drop unnecessary MFM-to-page conversions
> - drop a redundant call to destroy_xen_mappings() (an indentical call
> is being made a few lines up)
> - simplify a VA-to-MFN translation
> - drop dead code (several occurrences)
> - add a missing __init annotation
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Keir Fraser <keir@xen.org>
prev parent reply other threads:[~2013-01-16 15:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 15:39 [PATCH] miscellaneous cleanup Jan Beulich
2013-01-16 15:46 ` Keir Fraser [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=CD1C7BD1.58B6E%keir@xen.org \
--to=keir@xen.org \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).