From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] Patches for -next
Date: Fri, 21 May 2010 15:49:35 +0100 [thread overview]
Message-ID: <1274453375.7246.49.camel@e102109-lin.cambridge.arm.com> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB02C56FF34E@dbde02.ent.ti.com>
On Fri, 2010-05-21 at 11:57 +0100, Shilimkar, Santosh wrote:
> Catalin,
>
> > -----Original Message-----
> > From: Catalin Marinas [mailto:catalin.marinas at arm.com]
> > Sent: Friday, May 21, 2010 3:22 PM
> > To: Shilimkar, Santosh
> > Cc: Russell King - ARM Linux; linux-arm-kernel at lists.infradead.org
> > Subject: RE: [PATCH 0/4] Patches for -next
> >
> > Santosh,
> >
> > On Fri, 2010-05-21 at 06:59 +0100, Shilimkar, Santosh wrote:
> > > > Catalin Marinas (4):
> > > > ARM: Remove the domain switching on ARMv6k/v7 CPUs
> > > > ARM: Use lazy cache flushing on ARMv7 SMP systems
> > > > ARM: Assume new page cache pages have dirty D-cache
> > > > ARM: Defer the L_PTE_EXEC flag setting to update_mmu_cache() on SMP
> > > >
> > > >
> > > I just gave quick try with these patches on OMAP4 yesterday.
> > > "ARM: Defer the L_PTE_EXEC flag setting to update_mmu_cache() on SMP"
> > > patch is creating regression when loading the module.
> >
> > Thanks for testing and reporting this. I missed the fact the modules
> > allocation uses set_pte_at(). Below is an updated patch which makes sure
> > that L_PTE_EXEC is set for addresses greater than TASK_SIZE. We
> > shouldn't have a race for modules as initialisation only happens on a
> > single CPU.
> >
> > Could you please try the updated patch below?
> >
> This one works fine!!
> You can add, Tested-by: Santosh Shilimkar <Santosh.shilimkar@ti.com>
Thanks for testing.
Have you tried the whole series or just this one?
--
Catalin
next prev parent reply other threads:[~2010-05-21 14:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 14:29 [PATCH 0/4] Patches for -next Catalin Marinas
2010-05-20 14:30 ` [PATCH 1/4] ARM: Remove the domain switching on ARMv6k/v7 CPUs Catalin Marinas
2010-05-24 11:45 ` Russell King - ARM Linux
2010-05-24 13:25 ` Catalin Marinas
2010-05-24 13:52 ` Catalin Marinas
2010-05-24 13:59 ` Russell King - ARM Linux
2010-05-24 14:02 ` Catalin Marinas
2010-05-20 14:30 ` [PATCH 2/4] ARM: Use lazy cache flushing on ARMv7 SMP systems Catalin Marinas
2010-05-20 14:30 ` [PATCH 3/4] ARM: Assume new page cache pages have dirty D-cache Catalin Marinas
2010-05-20 14:30 ` [PATCH 4/4] ARM: Defer the L_PTE_EXEC flag setting to update_mmu_cache() on SMP Catalin Marinas
2010-05-21 5:59 ` [PATCH 0/4] Patches for -next Shilimkar, Santosh
2010-05-21 6:06 ` Shilimkar, Santosh
2010-05-21 9:52 ` Catalin Marinas
2010-05-21 10:57 ` Shilimkar, Santosh
2010-05-21 14:49 ` Catalin Marinas [this message]
2010-05-21 14:52 ` Shilimkar, Santosh
2010-05-21 19:04 ` Russell King - ARM Linux
2010-05-24 11:31 ` Catalin Marinas
2010-05-24 12:08 ` Russell King - ARM Linux
2010-05-24 13:06 ` Catalin Marinas
2010-05-26 13:06 ` Catalin Marinas
2010-05-26 18:28 ` Russell King - ARM Linux
2010-05-27 11:04 ` Catalin Marinas
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=1274453375.7246.49.camel@e102109-lin.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).