From: "Jan Beulich" <jbeulich@novell.com>
To: "Dave Airlie" <airlied@gmail.com>
Cc: "Dave Airlie" <airlied@linux.ie>, <linux-kernel@vger.kernel.org>
Subject: Re: agp: two-stage page destruction issue
Date: Thu, 19 Jun 2008 10:46:29 +0100 [thread overview]
Message-ID: <485A4715.76E4.0078.0@novell.com> (raw)
In-Reply-To: <21d7e9970806181657l79fa4e43oc42f23a18a33c4ee@mail.gmail.com>
>>> "Dave Airlie" <airlied@gmail.com> 19.06.08 01:57 >>>
>On Wed, Jun 18, 2008 at 6:28 PM, Jan Beulich <jbeulich@novell.com> wrote:
>> Dave,
>>
>> besides it apparently being useful only in 2.6.24 (the changes in 2.6.25
>> really mean that it could be converted back to a single-stage mechanism),
>> I'm seeing an issue in Xen Dom0 kernels, which is caused by the calling
>> of gart_to_virt() in the second stage invocations of the destroy function.
>> I think that besides this being a real issue with Xen (where
>> unmap_page_from_agp() is not just a page table attribute change), this
>> also is invalid from a theoretical perspective: One should not assume that
>> gart_to_virt() is still valid after unmapping a page. So minimally (keeping
>> the 2-stage mechanism) a patch like the one below would be needed.
>>
>
>Looks good to me, its the simpler change for 2.6.26 at this point.
>
>Dave.
So if you're considering it even for 2.6.26, will you push it to Linus? That's
how I understand the process would generally work, or should I push it
in this case (in which case it might be good to know whether your above
statement should be translated into an Acked-by or Signed-off-by)?
Thanks, Jan
next prev parent reply other threads:[~2008-06-19 9:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 8:28 agp: two-stage page destruction issue Jan Beulich
2008-06-18 23:57 ` Dave Airlie
2008-06-19 9:46 ` Jan Beulich [this message]
2008-06-20 1:47 ` Dave Airlie
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=485A4715.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=linux-kernel@vger.kernel.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