From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alexey Starikovskiy <aystarik@gmail.com>
Cc: Alexey Starikovskiy <astarikovskiy@suse.de>,
"Zhao, Yakui" <yakui.zhao@intel.com>,
Sitsofe Wheeler <sitsofe@yahoo.com>, LenBrown <lenb@kernel.org>,
Linux-acpi@vger.kernel.org
Subject: Re: [PATCH] ACPI: EC: do transaction from interrupt context
Date: Fri, 26 Sep 2008 17:57:23 +0200 [thread overview]
Message-ID: <200809261757.24585.rjw@sisk.pl> (raw)
In-Reply-To: <48DD040B.9020807@gmail.com>
On Friday, 26 of September 2008, Alexey Starikovskiy wrote:
> Rafael J. Wysocki wrote:
> > On Friday, 26 of September 2008, Alexey Starikovskiy wrote:
> >
> >> Rafael J. Wysocki wrote:
> >>
> >>>> He refers to the ec->curr (former ec->t).
> >>>>
> >>> Hm, I'm not sure what the failing scenario in this case would be.
> >>>
> >> Last one was the thread of the stack is killed during transaction,
> >> thus stack vanishes and interrupt goes over freed memory.
> >>
> >
> > This isn't possible IMO. The thread is uninterruptible while waiting for the
> > transaction to finish (if I'm not mistaken).
> >
> Right, I already explained it to Yakui, this is why he only claims
> "ugly" now.
> > That said, we can still embed 'curr' in 'struct acpi_ec' and do
> > 'ec.curr = t' instead of 'ec->curr = &t' in acpi_ec_transaction_unlocked().
> > Now, if 'command' is embedded in 'curr', it will be sufficient to do
> > 'if (curr.command)' instead of doing 'if (ec->curr)', wherever applicable.
> >
> No, I like current way more. Now it is not possible to use transaction
> data if
> acpi_ec_transaction is not on the stack.
OK
next prev parent reply other threads:[~2008-09-26 15:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 17:00 [PATCH] ACPI: EC: do transaction from interrupt context Alexey Starikovskiy
2008-09-25 17:52 ` Sitsofe Wheeler
2008-09-26 1:06 ` Zhao Yakui
2008-09-26 5:42 ` Sitsofe Wheeler
2008-09-26 6:01 ` Alexey Starikovskiy
2008-09-26 9:03 ` Alan Jenkins
2008-09-26 10:42 ` Alexey Starikovskiy
2008-09-26 11:17 ` Alan Jenkins
2008-09-26 6:04 ` Zhao Yakui
2008-09-26 12:33 ` Rafael J. Wysocki
2008-09-26 13:54 ` Zhao, Yakui
2008-09-26 14:15 ` Rafael J. Wysocki
2008-09-26 14:53 ` Alexey Starikovskiy
2008-09-26 15:18 ` Rafael J. Wysocki
2008-09-26 15:21 ` Alexey Starikovskiy
2008-09-26 15:48 ` Rafael J. Wysocki
2008-09-26 15:47 ` Alexey Starikovskiy
2008-09-26 15:57 ` Rafael J. Wysocki [this message]
2008-09-26 15:10 ` Zhao Yakui
2008-09-26 15:39 ` Rafael J. Wysocki
2008-09-27 3:39 ` Zhao Yakui
2008-09-27 5:37 ` Alexey Starikovskiy
2008-09-27 5:59 ` Zhao Yakui
2008-09-27 6:44 ` Alexey Starikovskiy
2008-09-25 20:10 ` Len Brown
-- strict thread matches above, loose matches on Subject: below --
2008-09-26 6:16 Sitsofe Wheeler
2008-09-25 11:24 Alexey Starikovskiy
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=200809261757.24585.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=Linux-acpi@vger.kernel.org \
--cc=astarikovskiy@suse.de \
--cc=aystarik@gmail.com \
--cc=lenb@kernel.org \
--cc=sitsofe@yahoo.com \
--cc=yakui.zhao@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox