From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bandan Das Subject: APIC_ID in apic_reg_write() Date: Wed, 29 Apr 2015 12:47:06 -0400 Message-ID: Mime-Version: 1.0 Content-Type: text/plain To: kvm@vger.kernel.org Return-path: Received: from mx1.redhat.com ([209.132.183.28]:39108 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965755AbbD2QrI (ORCPT ); Wed, 29 Apr 2015 12:47:08 -0400 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id t3TGl7dJ003866 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Wed, 29 Apr 2015 12:47:08 -0400 Received: from aqua (ovpn-113-178.phx2.redhat.com [10.3.113.178]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t3TGl6SD013742 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Wed, 29 Apr 2015 12:47:07 -0400 Sender: kvm-owner@vger.kernel.org List-ID: Why do we allow writes to APIC_ID ? On all _newer_ processors, it's read only. The spec doesn't explicitly mention it though, or atleast I couldn't find it. Does userspace have a reason to modify it ? Bandan