[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: xentrace buffer size, maxcpus and online cpus


  • To: Olaf Hering <olaf@xxxxxxxxx>
  • From: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
  • Date: Mon, 19 Jun 2023 12:14:21 +0100
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=citrix.com; dmarc=pass action=none header.from=citrix.com; dkim=pass header.d=citrix.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=NC3+4ERoCeGeZFeRZRsHuufbfSn5sgel0X9jz/QabYM=; b=MogKuRQFNumHypap1Mucfv1sbbI75QNagetOP0/zsuWB+jmCiUVwZlVLsTeA0iNZSVE0/dBVK3rIY4f3RDLRIfmlCTYuSLz1VTTAGdeBONbrzbibSvWgCr6/D4cP/lBpH4uR9aGEjigU26rJ/HdZTcweI3Yh3jG6tomndFXPasIrh7OvKEM4HIFKRNhHM3BRH+C1kxKuJ8NeTnde3AMjNpDBA+EkFfGn47hWaD+HnGNBybnWUb8vxZoqiiMzbfo0u7PLiczXjr3z6yOxQH65W9ihniF7AXUj3s+gkGsZHjBdqqu35ZUybNINnYyIGvXTZ9CdMzFFzojwq8bmjZGT9Q==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=HIcyUx9vOVqgxMzdUCx9CuCCueXqCaYAk+hgIIWPs5Pw+oCLG+XWcCgZhBheeWTIMmJxbFjxu7ZVKvZJcnQOKxziAvl+J6HsTjIU/PMqiEt5QAByzeDUVuVCTd+9tRZmPC5FRZlw6OKmbKMc1Kum7fBOXSjDorZZnlxeT54TR2nXjN1g81LmyFQSrU0fMT4ZV5ggbMOfEcH3rmoaChCzZuHthx6ijM3SXT3HQCY9WIL6aPYGWEi/B+M3hDq8rJCrF6qRRYgeX6yVK5gxoRVsbTht6M5jWsEYkFrJAEFcv8o9muBP5uIMU4RHA43PfR126tAx0RxDnSLAIz9hPGZ4Ow==
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=citrix.com;
  • Cc: George Dunlap <george.dunlap@xxxxxxxxx>, Jan Beulich <jbeulich@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx, Juergen Gross <jgross@xxxxxxxx>, George Dunlap <george.dunlap@xxxxxxxxxx>
  • Delivery-date: Mon, 19 Jun 2023 11:14:56 +0000
  • Ironport-data: A9a23:/8UYkKNT8fiX3TrvrR12lsFynXyQoLVcMsEvi/4bfWQNrUon1zYGy 2UfX2iDOf/bNjDxe95wa46x8UkDvcTcyYVmTQto+SlhQUwRpJueD7x1DKtS0wC6dZSfER09v 63yTvGacajYm1eF/k/F3oDJ9CU6jufQAOKnUoYoAwgpLSd8UiAtlBl/rOAwh49skLCRDhiE/ Nj/uKUzAnf8s9JPGjxSs/rrRC9H5qyo42tG5w1mPJingXeF/5UrJMNHTU2OByOQrrl8RoaSW +vFxbelyWLVlz9F5gSNy+uTnuUiG9Y+DCDW4pZkc/HKbitq/0Te5p0TJvsEAXq7vh3S9zxHJ HehgrTrIeshFvWkdO3wyHC0GQkmVUFN0OevzXRSLaV/ZqAJGpfh66wGMa04AWEX0vhUXDxys vYXEw02ZDSzn7i68uyyU/Y506zPLOGzVG8ekldJ6GiDSNwAEdXESaiM4sJE1jAtgMwIBezZe 8cSdTtoalLHfgFLPVAUTpk5mY9EhFGmK2Ee9A3T+PdxujeIpOBy+OGF3N79U9qGX8hK2G2fo XrL5T/RCRAGLt2PjzGC9xpAg8eWxHikAthJTeLQGvhC333D2Tw9BzovSgWF/Ke1yVSbS4x9N BlBksYphe1onKCxdfH6WxS2iHeJphAYVpxcHoUS5wyK0KXZpQqEAGwNVhZKbNs7uIk9QjlC/ l2Dks7tBDdvmKaIUn/b/bCRxRuiNC5QIWIcaCssSQoe/8KlsIw1lgjITNtoDOiylNKdMTP/2 TeRtwAlmq4ey8UM0s2GEUvvhjutot3DSF4z7wCOBGa9tFomP8iiepCi7kXd4bBYNoGFQ1Kdv X8C3c+D8OQJCpLLnyuIKAkQIIyUCz++GGW0qTZS81MJrlxBJ1bLkVhs3QxD
  • Ironport-hdrordr: A9a23:zOBiQq/OG7aneWR67FNuk+AcI+orL9Y04lQ7vn2ZKSY5TiX4rb HKoB1/73XJYVkqN03I9ervBEDiewK/yXcW2+ks1N6ZNWGLhILBFupfBODZsl7d8kPFl9K01c 1bAtJD4N+bNykGsS4tijPIb+rJw7O8gd+Vbf+19QYIcenzAZsQlzuQDGygYypLbTgDP7UVPr yG6PFKojKxEE5nFfhSVhE+Lo7+T8SgruOeXSI7
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 19/06/2023 11:16 am, Olaf Hering wrote:
> Fri, 16 Jun 2023 17:08:25 +0100 Andrew Cooper <andrew.cooper3@xxxxxxxxxx>:
>
>> XENMEM_acquire_resource is a new mapping interface with far more sane
>> semantics which, amongst other things, will work in PVH guests too.
> Does that indicate xentrace will not work in a PVH dom0?

To the best of my knowledge, it does not right now.

I seem to recall that ARM did some bodge to make it work for them, as
all guests are effectively PVH, but I don't recall exactly what that was.

> I will have a look how XENMEM_acquire_resource is used in other places.
> The resulting change will likely be too intrusive for 4.18.

It shouldn't be too bad IMO, but it's not the end of the world if it
falls into 4.19.

~Andrew



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.