public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Starikovskiy <aystarik@gmail.com>
To: "Moore, Robert" <robert.moore@intel.com>
Cc: Len Brown <lenb@kernel.org>,
	Alexey Starikovskiy <astarikovskiy@suse.de>,
	"Linux-acpi@vger.kernel.org" <Linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] ACPICA: Add hard limit to while loop
Date: Thu, 09 Oct 2008 21:42:55 +0400	[thread overview]
Message-ID: <48EE429F.8030903@gmail.com> (raw)
In-Reply-To: <4911F71203A09E4D9981D27F9D830858031232DF@orsmsx503.amr.corp.intel.com>

Moore, Robert wrote:
> The mutex and event opcodes come to mind, the AML can wait forever on these (Acquire, Wait). However, the interpreter is released when these opcodes block, quite unlike a spinning while loop.
>
> As far as infinite spin loops, I think While() is the only case. There is no GoTo AML operator, so loops cannot be artificially created.
>
> So, I think the loop counter idea is ok. Of course, picking a maximum number might be a bit difficult. 64K loop iterations takes 4-5 seconds on my machine here (in Ring 3). That is a lot of loops for AML code, it might be ok.
>
> Besides, we can say "nobody would ever need more than 64K loop iterations", and get ourselves in the computer hall of fame.  :-)
>
>   
Well, AML is not intended as general purpose OS/language, so we might be 
safe saying such things. :)
I would be extremely glad if Phoenix did not have enough 
resources/features to implement EC driver in AML in
first place :)

Regards,
Alex.

  reply	other threads:[~2008-10-09 17:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-09 10:35 [PATCH] ACPICA: Add hard limit to while loop Alexey Starikovskiy
2008-10-09 12:28 ` Moore, Robert
2008-10-09 14:55 ` Moore, Robert
2008-10-09 16:15   ` Moore, Robert
2008-10-09 16:32     ` Len Brown
2008-10-09 16:49       ` Moore, Robert
2008-10-09 17:42         ` Alexey Starikovskiy [this message]
2008-10-09 17:38     ` 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=48EE429F.8030903@gmail.com \
    --to=aystarik@gmail.com \
    --cc=Linux-acpi@vger.kernel.org \
    --cc=astarikovskiy@suse.de \
    --cc=lenb@kernel.org \
    --cc=robert.moore@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