[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Garbled output from kgdb?
- To: John Baldwin <jhb_(_at_)_freebsd_(_dot_)_org>
- Subject: Re: Garbled output from kgdb?
- From: Jung-uk Kim <jkim_(_at_)_FreeBSD_(_dot_)_org>
- Date: Mon, 11 May 2009 13:44:59 -0400
- Cc: Alan Amesbury <amesbury_(_at_)_umn_(_dot_)_edu>, freebsd-acpi_(_at_)_freebsd_(_dot_)_org, freebsd-stable_(_at_)_freebsd_(_dot_)_org, Andriy Gapon <avg_(_at_)_icyb_(_dot_)_net_(_dot_)_ua>
On Monday 11 May 2009 09:52 am, John Baldwin wrote:
> On Tuesday 05 May 2009 5:43:01 pm Jung-uk Kim wrote:
> > On Tuesday 05 May 2009 04:09 pm, Jung-uk Kim wrote:
> > > On Tuesday 05 May 2009 12:51 pm, Andriy Gapon wrote:
> > > > BTW, this issue seems to be fixed in Jung-uk's acpi patches
> > > > for newer acpica imports, but it is not fixed both in
> > > > stable/7 and head.
> > >
> > > Yes, it was fixed in my patchsets long ago, which uses spin
> > > lock for AcpiOsAcquireLock(). :-)
> >
> > The attached patch is for -STABLE. Note that it is only compile
> > tested on amd64.
>
> This looks fine to test. The patch has gratuitous style changes I
> wouldn't include in a commit though.
It should work but I don't plan to commit it any time soon. :-) In
fact, the patch was meant to be a rewrite for new ACPI-CA, which
actually has a real mutex. Currently, mutex is emulated with
semaphore. The problem is semaphore has no concept of ownership
while mutex does, i.e., any thread can acquire/release it without
checking its ownership or order. FYI, the OSL API (ACPI_MUTEX_TYPE)
is finalized in ACPI-CA 20081204.
Jung-uk Kim
_______________________________________________
freebsd-acpi_(_at_)_freebsd_(_dot_)_org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to "freebsd-acpi-unsubscribe_(_at_)_freebsd_(_dot_)_org"
Visit your host, monkey.org