All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomar <tomar@linuxsmiths.com>
To: Mike Galbraith <efault@gmx.de>
Cc: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [BUG] Why does mwait_idle_with_hints() call MWAIT with interrupts disabled ?
Date: Mon, 11 Jul 2011 13:32:53 +0530	[thread overview]
Message-ID: <CAM3a_ypSgCuf_8z82MKAt=9DXhz5fih-QYMLCrOVf+bBGde4Rg@mail.gmail.com> (raw)
In-Reply-To: <1310271636.7643.33.camel@marge.simson.net>

Mike,
        Thanks for pointing. This explains it. I was looking at an
older manual which did not have mention of this ECX extension.

Thanks,
Tomar



> I got curious enough to blow an inch of virtual dust off the manual..
>
> Software_Delelopers_Manual_Volume:2A:Instruction_Set_Reference:A-M
>
> MWAIT for Address Range Monitoring
>
> For address-range monitoring, the MWAIT instruction operates with the MONITOR
> instruction. The two instructions allow the definition of an address at which to wait
> (MONITOR) and a implementation-dependent-optimized operation to commence at
> the wait address (MWAIT). The execution of MWAIT is a hint to the processor that it
> can enter an implementation-dependent-optimized state while waiting for an event
> or a store operation to the address range armed by MONITOR.
> ECX specifies optional extensions for the MWAIT instruction. EAX may contain hints
> such as the preferred optimized state the processor should enter.
> For Pentium 4 processors (CPUID signature family 15 and model 3), non-zero values
> for EAX and ECX are reserved. Later processors defined ECX=1 as a valid extension
> (see below).
>
> A store to the address range armed by the MONITOR instruction, an interrupt, an NMI
> or SMI, a debug exception, a machine check exception, the BINIT# signal, the INIT#
> signal, or the RESET# signal will exit the implementation-dependent-optimized
> state. An interrupt will cause the processor to exit only if the state was entered with
> interrupts enabled or if ECX=1.
>                   ^^^^^^^^^^^
>
>

      reply	other threads:[~2011-07-11  8:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-07  0:40 [BUG] Why does mwait_idle_with_hints() call MWAIT with interrupts disabled ? Tomar
2011-07-09  0:30 ` Linux Smiths
2011-07-10  4:20   ` Mike Galbraith
2011-07-11  8:02     ` Tomar [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='CAM3a_ypSgCuf_8z82MKAt=9DXhz5fih-QYMLCrOVf+bBGde4Rg@mail.gmail.com' \
    --to=tomar@linuxsmiths.com \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=venkatesh.pallipadi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.