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

Re: [PATCH] xen: Allow platform PCI interrupt to be shared


  • To: David Woodhouse <dwmw2@xxxxxxxxxxxxx>, Juergen Gross <jgross@xxxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, Paul Durrant <paul@xxxxxxx>
  • From: Andrew Cooper <Andrew.Cooper3@xxxxxxxxxx>
  • Date: Wed, 18 Jan 2023 13:53:28 +0000
  • Accept-language: en-GB, en-US
  • 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=IaoY67JsHFpV6s+3TV4anSJ6LQ9em/1iMVNn2PRymjA=; b=miWl7DDHmPt0eafQd5DRVNnmIqqe32OBVeaa/WX+AO4vEAiPl8amy1r72NI9/x/XHMq/KQAWNCPqpf+zVPkgJqp1N6/TD0uRprgEYgGpUxFgjTRYeh/ULKbZWFNyvXjLBh5eOOTPAxSKh1qvqTrEe5SRQjn+owm22fTJNO2Z1oLgzMaXZFcKPTT5dygYrwM1ZvYwb2fuO2lpRnIzuCOyKEqj8xIZPFsO5lDVR3wOThiuATAjFp7pSTOhyfhGjVeUEQwbwFhTBiHgkUdA0z0xj1lyycHKbxIFzk8ulH/BCaSNGyNsm5YbyvsWfOalaW8oIayBLmFjRSfMBb/Fz+jvew==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=GQ9Wv/VcEnb3xJTqUCCOdFReAQhyhHKQhteYE7x2tRXX7ozIm1dgjmTJD1oFRi+fL7HBnXtSRrjTvaRrqLv7f3NO7KReY/LfeaCxKbP+Ko+W97X4/L8Kq08qakN5gPE5oLrxun7aFICWP0NYHbUy+K1wxkid/sQIb26p0yySD2R01eRo9+CJTMAUSjMi254v+eClDiltjQ0GVJfFjnzrAAvBnQjv87lKmhvnRdvSwVf1S4bfK6p5bH1Le4qLx8fBCtef78Bh0JpEYpGrWQ6OzXRByUezn2uU/O4bkAQdlk1XmjQAX+ANKe1iC8n5v7tP0p6FNfa7U1p7SIpKELXDxQ==
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=citrix.com;
  • Delivery-date: Wed, 18 Jan 2023 13:54:12 +0000
  • Ironport-data: A9a23:2oPCqarf2jjsHIJZIIpb4NKgmR9eBmKYZBIvgKrLsJaIsI4StFCzt garIBmFOPyNa2SheNtxbt7i80MF7JHRndRlTAptqng3FCgap5uZCYyVIHmrMnLJJKUvbq7FA +Y2MYCccZ9uHhcwgj/3b9ANeFEljfngqoLUUbKCYWYpAFc+E0/NsDo788YhmIlknNOlNA2Ev NL2sqX3NUSsnjV5KQr40YrawP9UlKm06WxwUmAWP6gR5weHzilNUPrzGInqR5fGatgMdgKFb 76rIIGRpgvx4xorA9W5pbf3GmVirmn6ZFXmZtJ+AsBOszAazsAA+v9T2Mk0MC+7vw6hjdFpo OihgLTrIesf0g8gr8xGO/VQO3kW0aSrY9YrK1Dn2SCY5xWun3cBX5yCpaz5VGEV0r8fPI1Ay RAXACJQdAyli/Do+p/hRutQj/seB463DIxK7xmMzRmBZRonabbqZv2WoPN9gnI3jM0IGuvCb c0EbzYpdA7HfxBEJlYQDtQ5gfusgX78NTZfrTp5p4JuuzSVkFM3j+OrbIK9lt+iHK25mm6xo G7c8nu/KRYdLNGFkhKO8262h/+JliT+MG4XPOzjq6472QLOroAVIDMuWmXio9Wzs0+jdI9We 2wb3ykN7qdnoSRHSfG4BXVUukWssgEZRIB4Eus08giBx6PYpQGDCQAsTDFbb8c9nNQrXjFs3 ViM9/vyHiBmurCRTXOb95+XoCm0NCxTKnUNDQcUQA1A79T9rYUbihPUUs0lAKOzlsfyGzz73 3aNtidWr7ESi9Mbkqa251bKhxqyqZXTCA04/APaWiSi9AwRTJKqY5yA7Vnd8OpaK4CYXh+Ns RAsg8GD6MgeAJfLkzaCKNjhB5ms7veBdTHZ31hmGsF98yz3oyL7O4dN/Dt5OUFldN4efiPka 1PSvgUX44JPOHytbul8ZIfZ59kW8JUM3O/NDpj8BueiqLArHONb1EmCvXKt4l0=
  • Ironport-hdrordr: A9a23:NY+LAandlJEhq/hollOUjySyqajpDfI73DAbv31ZSRFFG/Fw9v re/8jzsCWe4gr5N0tQ++xoR5PwJE80maQZ3WBzB9eftWvd1ldARbsKhbcKpQeNJ8SUzI9gPM lbHJSWAeeAaWRHsQ==
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Thread-index: AQHZKze3xTuOiK3Or0K7Zn5gBYHKJq6kMguA
  • Thread-topic: [PATCH] xen: Allow platform PCI interrupt to be shared

On 18/01/2023 12:22 pm, David Woodhouse wrote:
> Signed-off-by: David Woodhouse <dwmw@xxxxxxxxxxxx>
> ---
> What does xen_evtchn_do_upcall() exist for? Can we delete it? I don't
> see it being called anywhere.

Seems the caller was dropped by
cb09ea2924cbf1a42da59bd30a59cc1836240bcb, but the CONFIG_PVHVM looks
bogus because the precondition to setting it up was being in a Xen HVM
guest, and the guest is taking evtchns by vector either way.

PV guests use the entrypoint called exc_xen_hypervisor_callback which
really ought to gain a PV in its name somewhere.  Also the comments look
distinctly suspect.

Some tidying in this area would be valuable.

~Andrew

 


Rackspace

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