From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1827EC433F5 for ; Wed, 23 Feb 2022 17:42:56 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243433AbiBWRnW (ORCPT ); Wed, 23 Feb 2022 12:43:22 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:32954 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243117AbiBWRnW (ORCPT ); Wed, 23 Feb 2022 12:43:22 -0500 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id F0B914131D for ; Wed, 23 Feb 2022 09:42:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1645638173; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=qRjIpFpl+Y8ZaB7CKEGYDkJ5geifVDa7MyqJpWBf+L4=; b=HUPm+bE0QDTQhMDELIZs6BnR0/P2kaRMiFQ9wAwPf5mbkOIDpevduxe91h7sT4MV2JfYch zsQB1hmKPMvW6KcR7DlsmPrqWKi/V7+KFLb4io+JbRmhXg/YTcp0M33ZRNwFAX4ccTkKVR crvzx/0SNpvE9Q2psxE6OlrPhccZADg= Received: from mail-oo1-f70.google.com (mail-oo1-f70.google.com [209.85.161.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-553-lgubsoHXO8O1lN5milbAdg-1; Wed, 23 Feb 2022 12:42:51 -0500 X-MC-Unique: lgubsoHXO8O1lN5milbAdg-1 Received: by mail-oo1-f70.google.com with SMTP id c23-20020a4ad217000000b0031bec3c46deso9938242oos.0 for ; Wed, 23 Feb 2022 09:42:51 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:organization:mime-version:content-transfer-encoding; bh=qRjIpFpl+Y8ZaB7CKEGYDkJ5geifVDa7MyqJpWBf+L4=; b=PGBV8KXwY4NDTGxeWTgHS3Mhj9chDVu2NLOIPVHGvlanxUJ50Y8X1BQafjUwy9Eeco UlLZvqvVMfGY7oBQSz5eYrsum7lC7vFL8uiuYvOUySgac6fqBmu1m38QigHD+xw7FRSg kl4h16Bf1KuWNjIUeoYVTvrubOq1dQ3ToNlYXwOgVW6vdr9I8IwrUoWDfmpMrSptPmu9 cCml0pMtZFHlQ+w+cHEQ46v4kMmXtApTnfqOVMuQ7neqCrLBDTJ79bmW2hblNgQc9juX BhS/LvaSYC4xzygP6SKjbN2btZV5xkpuJbNP5dkMxkEMpfzqG1Uywbm10aSJHN2XNIvi eB/Q== X-Gm-Message-State: AOAM533UOCJZg/YBA6nVWX80+imWejHO8WpFs9XOI2SvPji/twWb8LRA Soo86fsqEpdQjWprpVPasRVlLMf+Alps9/uY5jdFj9Zu4Ps8dqM2syUfcilIe0RmUXbQh5F0m0s mxnG6F94qkAop+w3VCRFk X-Received: by 2002:a05:6870:6106:b0:d4:473f:7671 with SMTP id s6-20020a056870610600b000d4473f7671mr310506oae.327.1645638170977; Wed, 23 Feb 2022 09:42:50 -0800 (PST) X-Google-Smtp-Source: ABdhPJxq0hTPAXAa/qHrjN+Zp6BCaCXgRevYM49duz7eMMH+DpMmv9okVH5/L0hZhHRf8S2uYX0pUw== X-Received: by 2002:a05:6870:6106:b0:d4:473f:7671 with SMTP id s6-20020a056870610600b000d4473f7671mr310487oae.327.1645638170742; Wed, 23 Feb 2022 09:42:50 -0800 (PST) Received: from redhat.com ([38.15.36.239]) by smtp.gmail.com with ESMTPSA id n11sm125550oal.1.2022.02.23.09.42.49 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 23 Feb 2022 09:42:50 -0800 (PST) Date: Wed, 23 Feb 2022 10:42:48 -0700 From: Alex Williamson To: Yishai Hadas Cc: , , , , , , , , , , , , , , Subject: Re: [PATCH V8 mlx5-next 10/15] vfio: Extend the device migration protocol with RUNNING_P2P Message-ID: <20220223104248.62b7ad12.alex.williamson@redhat.com> In-Reply-To: <20220220095716.153757-11-yishaih@nvidia.com> References: <20220220095716.153757-1-yishaih@nvidia.com> <20220220095716.153757-11-yishaih@nvidia.com> Organization: Red Hat MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org On Sun, 20 Feb 2022 11:57:11 +0200 Yishai Hadas wrote: > diff --git a/include/linux/vfio.h b/include/linux/vfio.h > index 3bbadcdbc9c8..3176cb5d4464 100644 > --- a/include/linux/vfio.h > +++ b/include/linux/vfio.h > @@ -33,6 +33,7 @@ struct vfio_device { > struct vfio_group *group; > struct vfio_device_set *dev_set; > struct list_head dev_set_list; > + unsigned int migration_flags; Maybe paranoia, but should we sanity test this in __vfio_register_dev() to reinforce to driver authors that not all bit combinations are valid? Thanks, Alex