From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756186AbcECTQq (ORCPT ); Tue, 3 May 2016 15:16:46 -0400 Received: from mail-bl2on0057.outbound.protection.outlook.com ([65.55.169.57]:10569 "EHLO na01-bl2-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753015AbcECTQk convert rfc822-to-8bit (ORCPT ); Tue, 3 May 2016 15:16:40 -0400 From: "Saxena, Nitin" To: "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" Subject: VFIO MSIX Query Thread-Topic: VFIO MSIX Query Thread-Index: AQHRpWuMyItk3Q+kOUGwCyk/hje5qg== Date: Tue, 3 May 2016 18:42:31 +0000 Message-ID: <3517EB80-0AE6-4F54-AC0B-C1D0DC01158C@caviumnetworks.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=Nitin.Saxena@caviumnetworks.com; x-originating-ip: [49.204.225.32] x-ms-office365-filtering-correlation-id: 108f68c5-bfbc-4091-28d5-08d37382afba x-microsoft-exchange-diagnostics: 1;BLUPR0701MB1745;5:7CMH2gu0bDnqWQEr8dCJFIWiizN7jEEz5/vYhohno6dK+YUX1a6adNfFuKrk/QtJCGt7scnNAjtqx/c2IlQbuoCwOpF8R7SEqL+OqPCXLWMFH2x39Hhfyn3ZoxNRECRIGnqLR2GJRT31EXOolHNMKw==;24:u5dO6LvpIUrzEYHfizbTaxsshwBrpbPN/2w2+siDW0XtIDl1yzxip17vUqA1sIA2rxS3ddKLn4x8hCFD6SAtV3mK++9juZlhOMVUfgUmlkw=;7:6aejQEh8Tq2wHrg/1/NYF39j5tmjbpIzuXQInW0im1uwbgHxqwlMgUswdpO8rLlUxBPo/uxNawhRJ6PhPiL2awKvgFmNmAhpiXT0yeEv8kDcuihJ+nlmhaAHjp3Ja6yq+SPDx5Rf9I12e/xO5cXEsLpc0nDr02fLTX9oTsOwzBiqVw6RY3sJVz1IOx3KFbbp x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR0701MB1745; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(9101521096)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046);SRVR:BLUPR0701MB1745;BCL:0;PCL:0;RULEID:;SRVR:BLUPR0701MB1745; x-forefront-prvs: 0931CB1479 x-forefront-antispam-report: SFV:NSPM;SFS:(10009020)(979002)(6009001)(87936001)(2906002)(3660700001)(107886002)(2900100001)(83716003)(3280700002)(189998001)(77096005)(10400500002)(5008740100001)(11100500001)(5004730100002)(99286002)(106116001)(33656002)(2501003)(229853001)(66066001)(92566002)(50986999)(5001770100001)(86362001)(122556002)(36756003)(1220700001)(586003)(3480700004)(3846002)(6116002)(81166005)(82746002)(102836003)(8936002)(5002640100001)(54356999)(104396002)(217873001)(969003)(989001)(999001)(1009001)(1019001);DIR:OUT;SFP:1101;SCL:1;SRVR:BLUPR0701MB1745;H:BLUPR0701MB1746.namprd07.prod.outlook.com;FPR:;SPF:None;MLV:ovrnspm;PTR:InfoNoRecords;LANG:en; spamdiagnosticoutput: 1:23 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-ID: <21B82B2B49F77D4B89BA25695DEB8B53@caviumnetworks.microsoftonline.com> Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 X-OriginatorOrg: caviumnetworks.com X-MS-Exchange-CrossTenant-originalarrivaltime: 03 May 2016 18:42:31.8496 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 711e4ccf-2e9b-4bcf-a551-4094005b6194 X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR0701MB1745 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, I am a newbie to VFIO framework and trying to use it for MSIX interrupt handling in my userspace application. My userspace application is like intel's dpdk. My query is why vfio kernel code does not support msix masking/ unmasking i.e VFIO_SET_ACTION_TRIGGER is not implemented in kernel vfio code for MSIX but its present for legacy INTX? Another question since MSIX interrupt masking is absent in kernel who is supposed to mask/unmask msix interrupt? does userspace needs to mask/unmask interrupt after getting notified by eventfd. Is there any usecase where MSIX handling is done via VFIO framework? Thanks, Nitin Regards, Nitin