From: Olaf Hering <olaf@aepfle.de>
To: Keir Fraser <keir@xen.org>
Cc: xen-devel@lists.xensource.com, George Dunlap <george.dunlap@citrix.com>
Subject: Re: [PATCH 4 of 5] Update __insert_record() to copy the trace record to individual mfns
Date: Mon, 9 May 2011 11:31:05 +0200 [thread overview]
Message-ID: <20110509093105.GA16894@aepfle.de> (raw)
In-Reply-To: <C9ED6C60.2D18C%keir@xen.org>
On Mon, May 09, Keir Fraser wrote:
> On 06/05/2011 19:25, "Olaf Hering" <olaf@aepfle.de> wrote:
>
> > # HG changeset patch
> > # User Olaf Hering <olaf@aepfle.de>
> > # Date 1304700881 -7200
> > # Node ID 1c5da4d9e33c821b9e3276d7aefe7ee16ce7b162
> > # Parent 1631b61acaa8e88437d0f1861409ab1824de2721
> > Update __insert_record() to copy the trace record to individual mfns.
> > This is a prereq before changing the per-cpu allocation from contiguous
> > to non-contiguous allocation.
>
> I applied the trivial patches 1-3. I'll wait for Acks from George for
> patches 4-5.
Thanks Keir.
There are still issues with large buffers, I will post a new series.
Olaf
next prev parent reply other threads:[~2011-05-09 9:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 18:25 [PATCH 0 of 5] xentrace: non-contiguous allocation of per-cpu buffer Olaf Hering
2011-05-06 18:25 ` [PATCH 1 of 5] Move the global variable t_info_first_offset into calculate_tbuf_size() Olaf Hering
2011-05-06 18:25 ` [PATCH 2 of 5] Mark data_size __read_mostly because its only written once Olaf Hering
2011-05-06 18:25 ` [PATCH 3 of 5] Remove unneeded cast when assigning pointer value to dst Olaf Hering
2011-05-06 18:25 ` [PATCH 4 of 5] Update __insert_record() to copy the trace record to individual mfns Olaf Hering
2011-05-09 9:03 ` Keir Fraser
2011-05-09 9:31 ` Olaf Hering [this message]
2011-05-09 11:24 ` George Dunlap
2011-05-06 18:25 ` [PATCH 5 of 5] Allocate non-contiguous per-cpu trace buffers Olaf Hering
2011-05-08 15:07 ` [PATCH 0 of 5] xentrace: non-contiguous allocation of per-cpu buffer Olaf Hering
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=20110509093105.GA16894@aepfle.de \
--to=olaf@aepfle.de \
--cc=george.dunlap@citrix.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xensource.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 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.