From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from linux.microsoft.com (linux.microsoft.com [13.77.154.182]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 795AB19E97B; Wed, 25 Feb 2026 22:04:54 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=13.77.154.182 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772057095; cv=none; b=hK1JWPqMvIUY5Di48n/32rtFnP7MWE6I2jDXIaao71yX/SKwKwLQiJvbSTl7ZJDoP2ayRvD0TkFFQOVv6+HKfFfrHeqCpzxoQqsGC2qfNGojgnQFYXd1MPVXYEtgJEa8aTB7ezx4y4zIt8Ef1sIaVBkOhGlqNQdJ/KNuUUatl3Y= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772057095; c=relaxed/simple; bh=7VmOFNnhsrqi/GUBwUQHVsPUMsSjdfPWvEvPxrrj8Mc=; h=Message-ID:Date:MIME-Version:To:From:Cc:Subject:Content-Type; b=uVbMokQH0dz4lLxoUdtqciPf54RvmGnYXKiuFjWsRUMmHKpKA6apGqcQLlrmbUI9D7CdlMeldHskWg36A/45CXkKtXGGcyHVwWdDslHZhlJS9FG9Hl2Oskn2XfPlKTUurJsQklapdQcdjRWTukzImU723qCTmNXvBq6gvUXxXQc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.microsoft.com; spf=pass smtp.mailfrom=linux.microsoft.com; dkim=pass (1024-bit key) header.d=linux.microsoft.com header.i=@linux.microsoft.com header.b=QnMhc20k; arc=none smtp.client-ip=13.77.154.182 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.microsoft.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.microsoft.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.microsoft.com header.i=@linux.microsoft.com header.b="QnMhc20k" Received: from [192.168.0.88] (192-184-212-33.fiber.dynamic.sonic.net [192.184.212.33]) by linux.microsoft.com (Postfix) with ESMTPSA id DAC6B20B6F02; Wed, 25 Feb 2026 14:04:49 -0800 (PST) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com DAC6B20B6F02 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1772057090; bh=7VmOFNnhsrqi/GUBwUQHVsPUMsSjdfPWvEvPxrrj8Mc=; h=Date:To:From:Cc:Subject:From; b=QnMhc20kOq+nezuINr3Zhkbu5oELv2qVQeLz5d6elQyJM47y7GzGuzvyVM9h9MsXX FLUb4+zlMLWdWY0mJS7Lbs8BiDDpHrwxbcyNc45o9xX6J/UwQakPAIwq4sciZyiYNk J3HuQPXltUeoOgtROXdKy0HVOfVLk8cAoTopS/+w= Message-ID: <1f50dae2-ec4a-7914-a14f-2ada803eb0e3@linux.microsoft.com> Date: Wed, 25 Feb 2026 14:04:49 -0800 Precedence: bulk X-Mailing-List: linux-hyperv@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.13.1 Content-Language: en-US To: alex@shazbot.org From: Mukesh R Cc: kvm@vger.kernel.org, "wei.liu@kernel.org" , "linux-hyperv@vger.kernel.org" Subject: VFIO support on hyperv (vfio_pci_core_ioctl()) Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi Alex et al: I've been looking at making pci passthru irq setup/remap work on hyperv for the latest (6.19) version using vfio core. Unfortunately, it's just not fitting well because in case of hyperv the irq remap is done by the hypervisor. Specifically, for a robust and proper solution, we need to override vfio_pci_set_msi_trigger(). As such, for the best way forward I am trying to figure how much flexibility there is to modify vfio_pci_intrs.c with "if (running_on_hyperv())" branches (putting hyperv code in separate file). If none, then the alternative would be to create vfio-hyperv.c with vfio_device_ops.ioctl = hyperv_vfio_pci_core_ioctl(). But, then I'd be replicating code for other sub ioctls like vfio_pci_ioctl_get_info(), vfio_pci_ioctl_get_irq_info(), etc. Would it be acceptable to make them non static in this case? Please let me know your thoughts or if you have other suggestions. Thanks, -Mukesh