From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: lockdep: how to tell it multiple pte locks is OK?
Date: Mon, 08 Oct 2007 17:20:41 -0700 [thread overview]
Message-ID: <470AC959.1050508@goop.org> (raw)
In-Reply-To: <20071007104658.655565e3@laptopd505.fenrus.org>
Arjan van de Ven wrote:
> s/implemented/merged/ :)
>
> IN fact shared pagetables are already there for hugepages.
> For small pages it's a patch at this point.
>
Is it kept up to date? Where does it live?
> no I'm not saying that. I'm just saying that I'm worried about the
> locking robustness of your trick in general.
>
Hm, well I won't need to re-pin shared ptes anyway, so I think it's moot.
J
prev parent reply other threads:[~2007-10-09 0:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-07 6:31 lockdep: how to tell it multiple pte locks is OK? Jeremy Fitzhardinge
2007-10-07 8:29 ` Peter Zijlstra
2007-10-07 15:06 ` Jeremy Fitzhardinge
2007-10-07 16:58 ` Arjan van de Ven
2007-10-07 17:17 ` Jeremy Fitzhardinge
2007-10-07 17:46 ` Arjan van de Ven
2007-10-09 0:20 ` Jeremy Fitzhardinge [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=470AC959.1050508@goop.org \
--to=jeremy@goop.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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