From: Wei Yang <richardw.yang@linux.intel.com>
To: Wei Yang <richardw.yang@linux.intel.com>
Cc: qemu-devel@nongnu.org, rth@twiddle.net, pbonzini@redhat.com,
mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/6] Refine exec
Date: Mon, 22 Apr 2019 08:59:25 +0800 [thread overview]
Message-ID: <20190422005925.GA26676@richard> (raw)
In-Reply-To: <20190321082555.21118-1-richardw.yang@linux.intel.com>
Ping for this trivial series.
On Thu, Mar 21, 2019 at 04:25:49PM +0800, Wei Yang wrote:
>This serial refine exec a little.
>
>Wei Yang (6):
> exec.c: replace hwaddr with uint64_t for better understanding
> exec.c: remove an unnecessary assert on PHYS_MAP_NODE_NIL in
> phys_map_node_alloc()
> exec.c: get nodes_nb_alloc with one MAX calculation
> exec.c: subpage->sub_section is already initialized to 0
> exec.c: correct the maximum skip value during compact
> exec.c: add a check between constants to see whether we could skip
>
> exec.c | 21 ++++++++++-----------
> 1 file changed, 10 insertions(+), 11 deletions(-)
>
>--
>2.19.1
--
Wei Yang
Help you, Help me
WARNING: multiple messages have this Message-ID (diff)
From: Wei Yang <richardw.yang@linux.intel.com>
To: Wei Yang <richardw.yang@linux.intel.com>
Cc: pbonzini@redhat.com, mst@redhat.com, qemu-devel@nongnu.org,
rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH 0/6] Refine exec
Date: Mon, 22 Apr 2019 08:59:25 +0800 [thread overview]
Message-ID: <20190422005925.GA26676@richard> (raw)
Message-ID: <20190422005925.FSvjr6QfLaW66XhQ6ITH0LPGQLx56IaLhiS3ViGqIUc@z> (raw)
In-Reply-To: <20190321082555.21118-1-richardw.yang@linux.intel.com>
Ping for this trivial series.
On Thu, Mar 21, 2019 at 04:25:49PM +0800, Wei Yang wrote:
>This serial refine exec a little.
>
>Wei Yang (6):
> exec.c: replace hwaddr with uint64_t for better understanding
> exec.c: remove an unnecessary assert on PHYS_MAP_NODE_NIL in
> phys_map_node_alloc()
> exec.c: get nodes_nb_alloc with one MAX calculation
> exec.c: subpage->sub_section is already initialized to 0
> exec.c: correct the maximum skip value during compact
> exec.c: add a check between constants to see whether we could skip
>
> exec.c | 21 ++++++++++-----------
> 1 file changed, 10 insertions(+), 11 deletions(-)
>
>--
>2.19.1
--
Wei Yang
Help you, Help me
next parent reply other threads:[~2019-04-22 0:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190321082555.21118-1-richardw.yang@linux.intel.com>
2019-04-22 0:59 ` Wei Yang [this message]
2019-04-22 0:59 ` [Qemu-devel] [PATCH 0/6] Refine exec Wei Yang
2019-08-19 3:06 ` Wei Yang
2019-08-22 10:25 ` Paolo Bonzini
2019-08-22 22:31 ` Wei Yang
[not found] ` <20190321082555.21118-3-richardw.yang@linux.intel.com>
2019-08-22 10:24 ` [Qemu-devel] [PATCH 2/6] exec.c: remove an unnecessary assert on PHYS_MAP_NODE_NIL in phys_map_node_alloc() Paolo Bonzini
2019-08-23 1:07 ` Wei Yang
2019-09-12 2:51 ` Wei Yang
2019-09-12 12:42 ` Paolo Bonzini
2019-09-12 23:02 ` Wei Yang
2019-09-13 9:12 ` Paolo Bonzini
2019-09-16 2:02 ` Wei Yang
2019-09-16 7:50 ` Paolo Bonzini
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=20190422005925.GA26676@richard \
--to=richardw.yang@linux.intel.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).