On Thu, Feb 8, 2018 at 2:41 PM, Jia-Ju Bai wrote:
>
>
> On 2018/2/8 18:20, Rafael J. Wysocki wrote:
>>
>> On Thursday, February 8, 2018 11:13:10 AM CET Chris Wilson wrote:
>>>
>>> Quoting Rafael J. Wysocki (2018-02-08 09:51:41)
On Thursday, January 25, 2018
On Thu, Feb 8, 2018 at 2:41 PM, Jia-Ju Bai wrote:
>
>
> On 2018/2/8 18:20, Rafael J. Wysocki wrote:
>>
>> On Thursday, February 8, 2018 11:13:10 AM CET Chris Wilson wrote:
>>>
>>> Quoting Rafael J. Wysocki (2018-02-08 09:51:41)
On Thursday, January 25, 2018 11:13:41 AM CET Jia-Ju Bai
On 2018/2/8 18:20, Rafael J. Wysocki wrote:
On Thursday, February 8, 2018 11:13:10 AM CET Chris Wilson wrote:
Quoting Rafael J. Wysocki (2018-02-08 09:51:41)
On Thursday, January 25, 2018 11:13:41 AM CET Jia-Ju Bai wrote:
After checking all possible call chains to acpi_os_execute here,
my
On 2018/2/8 18:20, Rafael J. Wysocki wrote:
On Thursday, February 8, 2018 11:13:10 AM CET Chris Wilson wrote:
Quoting Rafael J. Wysocki (2018-02-08 09:51:41)
On Thursday, January 25, 2018 11:13:41 AM CET Jia-Ju Bai wrote:
After checking all possible call chains to acpi_os_execute here,
my
On Thursday, February 8, 2018 11:13:10 AM CET Chris Wilson wrote:
> Quoting Rafael J. Wysocki (2018-02-08 09:51:41)
> > On Thursday, January 25, 2018 11:13:41 AM CET Jia-Ju Bai wrote:
> > > After checking all possible call chains to acpi_os_execute here,
> > > my tool finds that acpi_os_execute is
On Thursday, February 8, 2018 11:13:10 AM CET Chris Wilson wrote:
> Quoting Rafael J. Wysocki (2018-02-08 09:51:41)
> > On Thursday, January 25, 2018 11:13:41 AM CET Jia-Ju Bai wrote:
> > > After checking all possible call chains to acpi_os_execute here,
> > > my tool finds that acpi_os_execute is
Quoting Rafael J. Wysocki (2018-02-08 09:51:41)
> On Thursday, January 25, 2018 11:13:41 AM CET Jia-Ju Bai wrote:
> > After checking all possible call chains to acpi_os_execute here,
> > my tool finds that acpi_os_execute is never called in atomic context.
> > And acpi_os_execute calls
Quoting Rafael J. Wysocki (2018-02-08 09:51:41)
> On Thursday, January 25, 2018 11:13:41 AM CET Jia-Ju Bai wrote:
> > After checking all possible call chains to acpi_os_execute here,
> > my tool finds that acpi_os_execute is never called in atomic context.
> > And acpi_os_execute calls
On Thursday, January 25, 2018 11:13:41 AM CET Jia-Ju Bai wrote:
> After checking all possible call chains to acpi_os_execute here,
> my tool finds that acpi_os_execute is never called in atomic context.
> And acpi_os_execute calls acpi_debugger_create_thread
> which calls mutex_lock,
> thus it
On Thursday, January 25, 2018 11:13:41 AM CET Jia-Ju Bai wrote:
> After checking all possible call chains to acpi_os_execute here,
> my tool finds that acpi_os_execute is never called in atomic context.
> And acpi_os_execute calls acpi_debugger_create_thread
> which calls mutex_lock,
> thus it
After checking all possible call chains to acpi_os_execute here,
my tool finds that acpi_os_execute is never called in atomic context.
And acpi_os_execute calls acpi_debugger_create_thread
which calls mutex_lock,
thus it proves again that acpi_os_execute can
call functions which may sleep.
Thus
After checking all possible call chains to acpi_os_execute here,
my tool finds that acpi_os_execute is never called in atomic context.
And acpi_os_execute calls acpi_debugger_create_thread
which calls mutex_lock,
thus it proves again that acpi_os_execute can
call functions which may sleep.
Thus
12 matches
Mail list logo