From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dario Faggioli <dario.faggioli@citrix.com>
Subject: Re: [PATCH v2 0/4] VMX: Properly handle pi descriptor
 and per-cpu blocking list
Date: Fri, 24 Jun 2016 12:29:19 +0200
Message-ID: <1466764159.18398.95.camel@citrix.com>
References: <1464269954-8056-1-git-send-email-feng.wu@intel.com>
 <1464283240.21930.157.camel@citrix.com>
 <E959C4978C3B6342920538CF579893F0197009A6@SHSMSX103.ccr.corp.intel.com>
 <1466631187.18398.55.camel@citrix.com>
 <E959C4978C3B6342920538CF579893F01972E2A2@SHSMSX103.ccr.corp.intel.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2224817393651175413=="
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <E959C4978C3B6342920538CF579893F01972E2A2@SHSMSX103.ccr.corp.intel.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
 <mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
 <mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Errors-To: xen-devel-bounces@lists.xen.org
Sender: "Xen-devel" <xen-devel-bounces@lists.xen.org>
To: "Wu, Feng" <feng.wu@intel.com>, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: "Tian, Kevin" <kevin.tian@intel.com>, "keir@xen.org" <keir@xen.org>, "george.dunlap@eu.citrix.com" <george.dunlap@eu.citrix.com>, "andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>, "jbeulich@suse.com" <jbeulich@suse.com>
List-Id: xen-devel@lists.xenproject.org

--===============2224817393651175413==
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="=-i32KL7kx7FxAKWAcMF/R"

--=-i32KL7kx7FxAKWAcMF/R
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, 2016-06-24 at 06:33 +0000, Wu, Feng wrote:
> > -----Original Message-----
> > From: Dario Faggioli [mailto:dario.faggioli@citrix.com]
> > In your case, AFAICUI, it's:
> > =C2=A0- the vCPU should block, waiting for an event
> > =C2=A0- the event is _not_ arrived, so we indeed should block
> > =C2=A0- we do *not* block, due to some other reason
> >=20
> > That does not look right to me... what about the fact that we
> > wanted to
> > actually wait for the event? :-O
> I understand your point. In my understanding, currently, vcpu_block()
> is
> for guest's HLT operation, which means, guest has nothing to do. In
> this case, even we return (not blocking), seems the function is not
> broken.
>
So, basically, you're saying that the vcpu has nothing to do, and in
fact it executed an HLT instruction, and you want to let it continue to
run? :-O

Dario
--=20
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)


--=-i32KL7kx7FxAKWAcMF/R
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAABCAAGBQJXbQt/AAoJEBZCeImluHPujz4P/RjMR69CbEqW5/nL/FHocTl4
PiLfD4VFp/cRF6mdU/yn2zxrIOvUbt1c3IQJb9dXBdJcFJV5KUhGEsuGHUdA/RLa
N5t779+qa7cYFVYmk9qvC4v+bDhRh+19eVZgYvjlKynQZvXjj1S5DBikfZsix1Oa
uGkZhyWvDKfs4F7Kmupm88PTDPMJMRYvdn6wZc/iKn0E29Ol9wbLn/L/T7JtHq7B
C5OF8wbDVAogBLHkKUOmsr5ni6dZNm5+RJyn2Zeve/BlRF4O780bhZlQCd0PjWAy
8m0rvZFWVRJ0oUh2/kUIpmh2TlPio7qjQ/wzMYq7QzB7tYmuSh0vvM86rvyvQlpb
PUpqvO2BTliHMfypeJkcamjQPc6Uh5QkZCuPJa84dk/CVoqg3FCazTbdpgmAr3Sn
MtfBHi3BNfiYV9BZAmCJ7FlIhbnM0sR3CYQ3yHgEUhNG6VURyA+r1SpkKL2pvVwj
HcIWe0HkgiAvBwGUvT1jQwGxtrJddII90gOOJZKyjXPiMuvQaYyOCYL1Uncrrpbd
DXrb0N/GS2bI/iFihRNl7Mr9spooUQUt7azlvL3pHzh0UjUieVePA/MSXCB8uu2V
QRWjZeqEo1lktVfvbuyF6X6PG6OakKQTGTgOXcJ2iuoqKC0M9MAIUgYHc2fgZgvk
1u3IDG6dNgYUkP/Ru5ZG
=7pjT
-----END PGP SIGNATURE-----

--=-i32KL7kx7FxAKWAcMF/R--


--===============2224817393651175413==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs
IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9y
Zy94ZW4tZGV2ZWwK

--===============2224817393651175413==--