From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Taylor, Neal E" <Neal.Taylor@ca.com>
Cc: Konrad Rzeszutek Wilk <konrad@darnok.org>,
xen-devel <xen-devel@lists.xensource.com>,
"Kalev, Leonid" <Leonid.Kalev@ca.com>,
Tushar N Dave <tushar.n.dave@intel.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: Buffers not reachable by PCI
Date: Thu, 15 Dec 2011 11:12:24 -0500 [thread overview]
Message-ID: <20111215161224.GB7272@phenom.dumpdata.com> (raw)
In-Reply-To: <3E243B26F475504B9BB0BCC9728B0DA629E18ED1@USILMS110A.ca.com>
On Thu, Dec 15, 2011 at 02:40:32AM +0000, Taylor, Neal E wrote:
> Sure! But only if 3.0.4 is recent enough. However, that version does not have the code for the "free_bootmem" section of this patch so only the first line was actually tested. (Not that I could test the negative case if the code existed.)
>
> I'll test on a more recent version (your pick) tomorrow, should you prefer.
Just as long as your modified code has this:
alloc_bootmem_pages(PAGE_ALIGN(bytes));
then that is great!
(The free_bootmem we can ignore for the 3.0.4 kernel).
next prev parent reply other threads:[~2011-12-15 16:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 20:19 Buffers not reachable by PCI Taylor, Neal E
2011-12-09 20:30 ` Konrad Rzeszutek Wilk
2011-12-12 22:11 ` Taylor, Neal E
2011-12-13 0:19 ` Konrad Rzeszutek Wilk
2011-12-13 19:34 ` Taylor, Neal E
2011-12-13 22:17 ` Taylor, Neal E
2011-12-13 23:28 ` Konrad Rzeszutek Wilk
2011-12-14 0:38 ` Taylor, Neal E
2011-12-14 9:20 ` Jan Beulich
2011-12-14 16:42 ` Taylor, Neal E
2011-12-14 18:42 ` Kalev, Leonid
2011-12-15 1:59 ` Konrad Rzeszutek Wilk
2011-12-15 2:19 ` Taylor, Neal E
2011-12-15 2:29 ` Konrad Rzeszutek Wilk
2011-12-15 2:40 ` Taylor, Neal E
2011-12-15 16:12 ` Konrad Rzeszutek Wilk [this message]
2011-12-15 16:14 ` Taylor, Neal E
2011-12-15 2:16 ` Taylor, Neal E
2011-12-14 19:11 ` Konrad Rzeszutek Wilk
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=20111215161224.GB7272@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=Leonid.Kalev@ca.com \
--cc=Neal.Taylor@ca.com \
--cc=konrad@darnok.org \
--cc=tushar.n.dave@intel.com \
--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.