From: Huang Ying <ying.huang@intel.com>
To: Thomas Renninger <trenn@suse.de>
Cc: Myron Stowe <myron.stowe@redhat.com>,
"lenb@kernel.org" <lenb@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"rjw@sisk.pl" <rjw@sisk.pl>,
"bhelgaas@google.com" <bhelgaas@google.com>
Subject: Re: [PATCH 0/2] ACPI: Re-factor and remove ./drivers/acpi/atomicio.[ch]
Date: Fri, 04 Nov 2011 09:32:38 +0800 [thread overview]
Message-ID: <1320370358.24181.19.camel@yhuang-dev> (raw)
In-Reply-To: <201111040324.31692.trenn@suse.de>
On Fri, 2011-11-04 at 10:24 +0800, Thomas Renninger wrote:
> On Friday 04 November 2011 01:56:04 Huang Ying wrote:
> > On Fri, 2011-11-04 at 00:31 +0800, Thomas Renninger wrote:
> > > On Thursday, September 29, 2011 11:59:08 PM Myron Stowe wrote:
> > > > Late last year I submitted a patch series that re-factored some existing
> > > > work that Huang Ying introduced adding support for accessing ACPI
> > > > generic registers backed by Memory Mapped I/O (MMIO) while within
> > > > interrupt context:
> > > > Huang Ying's commit 15651291a2f8c11e7e6a42d8bfde7a213ff13262,
> > > > My series: http://marc.info/?l=linux-acpi&m=128769263327206&w=2.
> > >
> > > Ying: What is your opinion about this patchset?
> >
> > I am OK with the patchset.
> Great, thanks.
> > We just need some testing.
> Hm, that's what release candidates (-rcX) are for.
>
> > > One major change seem to be to use a mutex instead of a spinlock
> > > which looks like a fix as the pre-mapping should never happen in
> > > irq context.
> >
> > Sorry, where is the mutex?
> you used a spinlock in atomicio.c:
> static DEFINE_SPINLOCK(acpi_iomaps_lock);
> in osl.c a mutex is used:
> static DEFINE_MUTEX(acpi_ioremap_lock);
Thanks. I think mutex is OK here because it will not be used in IRQ/NMI
handler.
Best Regards,
Huang Ying
prev parent reply other threads:[~2011-11-04 1:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 21:59 [PATCH 0/2] ACPI: Re-factor and remove ./drivers/acpi/atomicio.[ch] Myron Stowe
2011-09-29 21:59 ` [PATCH 1/2] ACPI: Export interfaces for ioremapping/iounmapping ACPI registers Myron Stowe
2011-11-06 12:49 ` Rafael J. Wysocki
2011-09-29 21:59 ` [PATCH 2/2] ACPI: Convert acpi_pre_map_gar()/acpi_atomic_read() and remove ./drivers/acpi/atomicio.[ch] Myron Stowe
2011-11-06 13:05 ` Rafael J. Wysocki
2011-10-28 1:49 ` [PATCH 0/2] ACPI: Re-factor " Thomas Renninger
2011-10-28 15:03 ` Bjorn Helgaas
2011-10-31 10:47 ` Thomas Renninger
2011-11-03 1:42 ` Myron Stowe
2011-11-06 13:30 ` Rafael J. Wysocki
2011-11-04 23:54 ` Myron Stowe
2011-11-05 2:42 ` Thomas Renninger
2011-11-06 13:42 ` Rafael J. Wysocki
2011-11-15 18:45 ` Bjorn Helgaas
2011-11-06 13:25 ` Rafael J. Wysocki
2011-11-06 13:23 ` Rafael J. Wysocki
2011-10-28 15:14 ` Bjorn Helgaas
2011-10-31 10:33 ` Thomas Renninger
2011-10-31 15:51 ` Bjorn Helgaas
2011-11-03 9:16 ` Thomas Renninger
2011-11-03 13:53 ` Bjorn Helgaas
2011-11-03 16:18 ` Thomas Renninger
2011-11-03 16:44 ` Myron Stowe
2011-11-04 2:16 ` Thomas Renninger
2011-11-04 1:55 ` Myron Stowe
2011-10-28 22:40 ` Myron Stowe
2011-11-06 13:19 ` Rafael J. Wysocki
2011-11-03 16:31 ` Thomas Renninger
2011-11-04 0:56 ` Huang Ying
2011-11-04 2:24 ` Thomas Renninger
2011-11-04 1:32 ` Huang Ying [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=1320370358.24181.19.camel@yhuang-dev \
--to=ying.huang@intel.com \
--cc=bhelgaas@google.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=myron.stowe@redhat.com \
--cc=rjw@sisk.pl \
--cc=trenn@suse.de \
/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