public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: "Liu, Yi L" <yi.l.liu@intel.com>
Cc: "jgg@nvidia.com" <jgg@nvidia.com>,
	"Tian, Kevin" <kevin.tian@intel.com>,
	"joro@8bytes.org" <joro@8bytes.org>,
	"robin.murphy@arm.com" <robin.murphy@arm.com>,
	"cohuck@redhat.com" <cohuck@redhat.com>,
	"eric.auger@redhat.com" <eric.auger@redhat.com>,
	"nicolinc@nvidia.com" <nicolinc@nvidia.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"mjrosato@linux.ibm.com" <mjrosato@linux.ibm.com>,
	"chao.p.peng@linux.intel.com" <chao.p.peng@linux.intel.com>,
	"yi.y.sun@linux.intel.com" <yi.y.sun@linux.intel.com>,
	"peterx@redhat.com" <peterx@redhat.com>,
	"jasowang@redhat.com" <jasowang@redhat.com>,
	"shameerali.kolothum.thodi@huawei.com" 
	<shameerali.kolothum.thodi@huawei.com>,
	"lulu@redhat.com" <lulu@redhat.com>,
	"suravee.suthikulpanit@amd.com" <suravee.suthikulpanit@amd.com>,
	"intel-gvt-dev@lists.freedesktop.org" 
	<intel-gvt-dev@lists.freedesktop.org>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"linux-s390@vger.kernel.org" <linux-s390@vger.kernel.org>,
	"Hao, Xudong" <xudong.hao@intel.com>,
	"Zhao, Yan Y" <yan.y.zhao@intel.com>,
	"Xu, Terrence" <terrence.xu@intel.com>,
	"Jiang, Yanting" <yanting.jiang@intel.com>,
	"Duan, Zhenzhong" <zhenzhong.duan@intel.com>,
	"clegoate@redhat.com" <clegoate@redhat.com>
Subject: Re: [PATCH v13 21/22] vfio: Compile vfio_group infrastructure optionally
Date: Mon, 17 Jul 2023 12:45:39 -0600	[thread overview]
Message-ID: <20230717124539.743de027.alex.williamson@redhat.com> (raw)
In-Reply-To: <DS0PR11MB7529F01B82FB659B96D15E38C33BA@DS0PR11MB7529.namprd11.prod.outlook.com>

On Mon, 17 Jul 2023 08:08:59 +0000
"Liu, Yi L" <yi.l.liu@intel.com> wrote:

> > From: Liu, Yi L <yi.l.liu@intel.com>
> > Sent: Monday, July 17, 2023 2:36 PM
> >   
> > > From: Liu, Yi L <yi.l.liu@intel.com>
> > > Sent: Friday, June 16, 2023 5:40 PM
> > >
> > > vfio_group is not needed for vfio device cdev, so with vfio device cdev
> > > introduced, the vfio_group infrastructures can be compiled out if only
> > > cdev is needed.
> > >
> > > Tested-by: Nicolin Chen <nicolinc@nvidia.com>
> > > Tested-by: Matthew Rosato <mjrosato@linux.ibm.com>
> > > Tested-by: Yanting Jiang <yanting.jiang@intel.com>
> > > Tested-by: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
> > > Tested-by: Terrence Xu <terrence.xu@intel.com>
> > > Signed-off-by: Yi Liu <yi.l.liu@intel.com>
> > > ---
> > >  drivers/iommu/iommufd/Kconfig |  4 +-
> > >  drivers/vfio/Kconfig          | 15 ++++++
> > >  drivers/vfio/Makefile         |  2 +-
> > >  drivers/vfio/vfio.h           | 89 ++++++++++++++++++++++++++++++++---
> > >  include/linux/vfio.h          | 25 ++++++++--
> > >  5 files changed, 123 insertions(+), 12 deletions(-)
> > >
> > > diff --git a/drivers/iommu/iommufd/Kconfig b/drivers/iommu/iommufd/Kconfig
> > > index ada693ea51a7..99d4b075df49 100644
> > > --- a/drivers/iommu/iommufd/Kconfig
> > > +++ b/drivers/iommu/iommufd/Kconfig
> > > @@ -14,8 +14,8 @@ config IOMMUFD
> > >  if IOMMUFD
> > >  config IOMMUFD_VFIO_CONTAINER
> > >  	bool "IOMMUFD provides the VFIO container /dev/vfio/vfio"
> > > -	depends on VFIO && !VFIO_CONTAINER
> > > -	default VFIO && !VFIO_CONTAINER
> > > +	depends on VFIO_GROUP && !VFIO_CONTAINER
> > > +	default VFIO_GROUP && !VFIO_CONTAINER  
> > 
> > Hi Alex, Jason,
> > 
> > I found a minor nit on the kconfig. The below configuration is valid.
> > But user cannot use vfio directly as there is no /dev/vfio/vfio. Although
> > user can open /dev/iommu instead. This is not good.
> > 
> > CONFIG_IOMMUFD=y
> > CONFIG_VFIO_DEVICE_CDEv=n
> > CONFIG_VFIO_GROUP=y
> > CONFIG_VFIO_CONTAINER=n
> > CONFIG_IOMMUFD_VFIO_CONTAINER=n
> > 
> > So need to have the below change. I'll incorporate this change in
> > this series after your ack.
> > 
> > diff --git a/drivers/iommu/iommufd/Kconfig b/drivers/iommu/iommufd/Kconfig
> > index 99d4b075df49..d675c96c2bbb 100644
> > --- a/drivers/iommu/iommufd/Kconfig
> > +++ b/drivers/iommu/iommufd/Kconfig
> > @@ -14,8 +14,8 @@ config IOMMUFD
> >  if IOMMUFD
> >  config IOMMUFD_VFIO_CONTAINER
> >  	bool "IOMMUFD provides the VFIO container /dev/vfio/vfio"
> > -	depends on VFIO_GROUP && !VFIO_CONTAINER
> > -	default VFIO_GROUP && !VFIO_CONTAINER
> > +	depends on VFIO_GROUP
> > +	default n
> >  	help
> >  	  IOMMUFD will provide /dev/vfio/vfio instead of VFIO. This relies on
> >  	  IOMMUFD providing compatibility emulation to give the same ioctls.
> > diff --git a/drivers/vfio/Kconfig b/drivers/vfio/Kconfig
> > index 6bda6dbb4878..ee3bbad6beb8 100644
> > --- a/drivers/vfio/Kconfig
> > +++ b/drivers/vfio/Kconfig
> > @@ -6,7 +6,7 @@ menuconfig VFIO
> >  	select INTERVAL_TREE
> >  	select VFIO_GROUP if SPAPR_TCE_IOMMU || IOMMUFD=n
> >  	select VFIO_DEVICE_CDEV if !VFIO_GROUP
> > -	select VFIO_CONTAINER if IOMMUFD=n
> > +	select VFIO_CONTAINER if IOMMUFD_VFIO_CONTAINER=n
> >  	help
> >  	  VFIO provides a framework for secure userspace device drivers.
> >  	  See Documentation/driver-api/vfio.rst for more details.
> >   
> 
> Just realized that it is possible to config both VFIO_CONTAINER and
> IOMMUFD_VFIO_CONTAINER to "y". Then there will be a conflict when
> registering /dev/vfio/vfio. Any suggestion?

This is only an issue with the proposed change, right?  I agree with
Jason, removing /dev/vfio/vfio entirely should be possible.  That's
actually our ultimate goal, but obviously it breaks current userspace
depending on vfio container compatibility.  It's a configuration error,
not a Kconfig error if someone finds themselves without /dev/vfio/vfio
currently.  Thanks,

Alex

> > >  	help
> > >  	  IOMMUFD will provide /dev/vfio/vfio instead of VFIO. This relies on
> > >  	  IOMMUFD providing compatibility emulation to give the same ioctls.
> > > diff --git a/drivers/vfio/Kconfig b/drivers/vfio/Kconfig
> > > index 1cab8e4729de..35ab8ab87688 100644
> > > --- a/drivers/vfio/Kconfig
> > > +++ b/drivers/vfio/Kconfig
> > > @@ -4,6 +4,8 @@ menuconfig VFIO
> > >  	select IOMMU_API
> > >  	depends on IOMMUFD || !IOMMUFD
> > >  	select INTERVAL_TREE
> > > +	select VFIO_GROUP if SPAPR_TCE_IOMMU || IOMMUFD=n
> > > +	select VFIO_DEVICE_CDEV if !VFIO_GROUP
> > >  	select VFIO_CONTAINER if IOMMUFD=n  
> > 
> > This should be " select VFIO_CONTAINER if IOMMUFD_VFIO_CONTAINER=n"
> > 
> > Regards,
> > Yi Liu
> >   
> > >  	help
> > >  	  VFIO provides a framework for secure userspace device drivers.
> > > @@ -15,6 +17,7 @@ if VFIO
> > >  config VFIO_DEVICE_CDEV
> > >  	bool "Support for the VFIO cdev /dev/vfio/devices/vfioX"
> > >  	depends on IOMMUFD
> > > +	default !VFIO_GROUP
> > >  	help
> > >  	  The VFIO device cdev is another way for userspace to get device
> > >  	  access. Userspace gets device fd by opening device cdev under
> > > @@ -24,9 +27,20 @@ config VFIO_DEVICE_CDEV
> > >
> > >  	  If you don't know what to do here, say N.
> > >
> > > +config VFIO_GROUP
> > > +	bool "Support for the VFIO group /dev/vfio/$group_id"
> > > +	default y
> > > +	help
> > > +	   VFIO group support provides the traditional model for accessing
> > > +	   devices through VFIO and is used by the majority of userspace
> > > +	   applications and drivers making use of VFIO.
> > > +
> > > +	   If you don't know what to do here, say Y.
> > > +
> > >  config VFIO_CONTAINER
> > >  	bool "Support for the VFIO container /dev/vfio/vfio"
> > >  	select VFIO_IOMMU_TYPE1 if MMU && (X86 || S390 || ARM || ARM64)
> > > +	depends on VFIO_GROUP
> > >  	default y
> > >  	help
> > >  	  The VFIO container is the classic interface to VFIO for establishing
> > > @@ -48,6 +62,7 @@ endif
> > >
> > >  config VFIO_NOIOMMU
> > >  	bool "VFIO No-IOMMU support"
> > > +	depends on VFIO_GROUP
> > >  	help
> > >  	  VFIO is built on the ability to isolate devices using the IOMMU.
> > >  	  Only with an IOMMU can userspace access to DMA capable devices be
> > > diff --git a/drivers/vfio/Makefile b/drivers/vfio/Makefile
> > > index 245394aeb94b..57c3515af606 100644
> > > --- a/drivers/vfio/Makefile
> > > +++ b/drivers/vfio/Makefile
> > > @@ -2,9 +2,9 @@
> > >  obj-$(CONFIG_VFIO) += vfio.o
> > >
> > >  vfio-y += vfio_main.o \
> > > -	  group.o \
> > >  	  iova_bitmap.o
> > >  vfio-$(CONFIG_VFIO_DEVICE_CDEV) += device_cdev.o
> > > +vfio-$(CONFIG_VFIO_GROUP) += group.o
> > >  vfio-$(CONFIG_IOMMUFD) += iommufd.o
> > >  vfio-$(CONFIG_VFIO_CONTAINER) += container.o
> > >  vfio-$(CONFIG_VFIO_VIRQFD) += virqfd.o
> > > diff --git a/drivers/vfio/vfio.h b/drivers/vfio/vfio.h
> > > index e7a3fe093362..b27a3915e6c9 100644
> > > --- a/drivers/vfio/vfio.h
> > > +++ b/drivers/vfio/vfio.h
> > > @@ -36,6 +36,12 @@ vfio_allocate_device_file(struct vfio_device *device);
> > >
> > >  extern const struct file_operations vfio_device_fops;
> > >
> > > +#ifdef CONFIG_VFIO_NOIOMMU
> > > +extern bool vfio_noiommu __read_mostly;
> > > +#else
> > > +enum { vfio_noiommu = false };
> > > +#endif
> > > +
> > >  enum vfio_group_type {
> > >  	/*
> > >  	 * Physical device with IOMMU backing.
> > > @@ -60,6 +66,7 @@ enum vfio_group_type {
> > >  	VFIO_NO_IOMMU,
> > >  };
> > >
> > > +#if IS_ENABLED(CONFIG_VFIO_GROUP)
> > >  struct vfio_group {
> > >  	struct device 			dev;
> > >  	struct cdev			cdev;
> > > @@ -111,6 +118,82 @@ static inline bool vfio_device_is_noiommu(struct vfio_device
> > > *vdev)
> > >  	return IS_ENABLED(CONFIG_VFIO_NOIOMMU) &&
> > >  	       vdev->group->type == VFIO_NO_IOMMU;
> > >  }
> > > +#else
> > > +struct vfio_group;
> > > +
> > > +static inline int vfio_device_block_group(struct vfio_device *device)
> > > +{
> > > +	return 0;
> > > +}
> > > +
> > > +static inline void vfio_device_unblock_group(struct vfio_device *device)
> > > +{
> > > +}
> > > +
> > > +static inline int vfio_device_set_group(struct vfio_device *device,
> > > +					enum vfio_group_type type)
> > > +{
> > > +	return 0;
> > > +}
> > > +
> > > +static inline void vfio_device_remove_group(struct vfio_device *device)
> > > +{
> > > +}
> > > +
> > > +static inline void vfio_device_group_register(struct vfio_device *device)
> > > +{
> > > +}
> > > +
> > > +static inline void vfio_device_group_unregister(struct vfio_device *device)
> > > +{
> > > +}
> > > +
> > > +static inline int vfio_device_group_use_iommu(struct vfio_device *device)
> > > +{
> > > +	return -EOPNOTSUPP;
> > > +}
> > > +
> > > +static inline void vfio_device_group_unuse_iommu(struct vfio_device *device)
> > > +{
> > > +}
> > > +
> > > +static inline void vfio_df_group_close(struct vfio_device_file *df)
> > > +{
> > > +}
> > > +
> > > +static inline struct vfio_group *vfio_group_from_file(struct file *file)
> > > +{
> > > +	return NULL;
> > > +}
> > > +
> > > +static inline bool vfio_group_enforced_coherent(struct vfio_group *group)
> > > +{
> > > +	return true;
> > > +}
> > > +
> > > +static inline void vfio_group_set_kvm(struct vfio_group *group, struct kvm *kvm)
> > > +{
> > > +}
> > > +
> > > +static inline bool vfio_device_has_container(struct vfio_device *device)
> > > +{
> > > +	return false;
> > > +}
> > > +
> > > +static inline int __init vfio_group_init(void)
> > > +{
> > > +	return 0;
> > > +}
> > > +
> > > +static inline void vfio_group_cleanup(void)
> > > +{
> > > +}
> > > +
> > > +static inline bool vfio_device_is_noiommu(struct vfio_device *vdev)
> > > +{
> > > +	return false;
> > > +}
> > > +#endif /* CONFIG_VFIO_GROUP */
> > >
> > >  #if IS_ENABLED(CONFIG_VFIO_CONTAINER)
> > >  /**
> > > @@ -362,12 +445,6 @@ static inline void vfio_virqfd_exit(void)
> > >  }
> > >  #endif
> > >
> > > -#ifdef CONFIG_VFIO_NOIOMMU
> > > -extern bool vfio_noiommu __read_mostly;
> > > -#else
> > > -enum { vfio_noiommu = false };
> > > -#endif
> > > -
> > >  #ifdef CONFIG_HAVE_KVM
> > >  void _vfio_device_get_kvm_safe(struct vfio_device *device, struct kvm *kvm);
> > >  void vfio_device_put_kvm(struct vfio_device *device);
> > > diff --git a/include/linux/vfio.h b/include/linux/vfio.h
> > > index d6228c839c44..5a1dee983f17 100644
> > > --- a/include/linux/vfio.h
> > > +++ b/include/linux/vfio.h
> > > @@ -43,7 +43,11 @@ struct vfio_device {
> > >  	 */
> > >  	const struct vfio_migration_ops *mig_ops;
> > >  	const struct vfio_log_ops *log_ops;
> > > +#if IS_ENABLED(CONFIG_VFIO_GROUP)
> > >  	struct vfio_group *group;
> > > +	struct list_head group_next;
> > > +	struct list_head iommu_entry;
> > > +#endif
> > >  	struct vfio_device_set *dev_set;
> > >  	struct list_head dev_set_list;
> > >  	unsigned int migration_flags;
> > > @@ -58,8 +62,6 @@ struct vfio_device {
> > >  	refcount_t refcount;	/* user count on registered device*/
> > >  	unsigned int open_count;
> > >  	struct completion comp;
> > > -	struct list_head group_next;
> > > -	struct list_head iommu_entry;
> > >  	struct iommufd_access *iommufd_access;
> > >  	void (*put_kvm)(struct kvm *kvm);
> > >  #if IS_ENABLED(CONFIG_IOMMUFD)
> > > @@ -284,12 +286,29 @@ int vfio_mig_get_next_state(struct vfio_device *device,
> > >  /*
> > >   * External user API
> > >   */
> > > +#if IS_ENABLED(CONFIG_VFIO_GROUP)
> > >  struct iommu_group *vfio_file_iommu_group(struct file *file);
> > >  bool vfio_file_is_group(struct file *file);
> > > +bool vfio_file_has_dev(struct file *file, struct vfio_device *device);
> > > +#else
> > > +static inline struct iommu_group *vfio_file_iommu_group(struct file *file)
> > > +{
> > > +	return NULL;
> > > +}
> > > +
> > > +static inline bool vfio_file_is_group(struct file *file)
> > > +{
> > > +	return false;
> > > +}
> > > +
> > > +static inline bool vfio_file_has_dev(struct file *file, struct vfio_device *device)
> > > +{
> > > +	return false;
> > > +}
> > > +#endif
> > >  bool vfio_file_is_valid(struct file *file);
> > >  bool vfio_file_enforced_coherent(struct file *file);
> > >  void vfio_file_set_kvm(struct file *file, struct kvm *kvm);
> > > -bool vfio_file_has_dev(struct file *file, struct vfio_device *device);
> > >
> > >  #define VFIO_PIN_PAGES_MAX_ENTRIES	(PAGE_SIZE/sizeof(unsigned long))
> > >
> > > --
> > > 2.34.1  
> 


  reply	other threads:[~2023-07-17 18:46 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-16  9:39 [PATCH v13 00/22] Add vfio_device cdev for iommufd support Yi Liu
2023-06-16  9:39 ` [PATCH v13 01/22] vfio: Allocate per device file structure Yi Liu
2023-06-16  9:39 ` [PATCH v13 02/22] vfio: Refine vfio file kAPIs for KVM Yi Liu
2023-06-16  9:39 ` [PATCH v13 03/22] vfio: Accept vfio device file in the KVM facing kAPI Yi Liu
2023-06-16  9:39 ` [PATCH v13 04/22] kvm/vfio: Prepare for accepting vfio device fd Yi Liu
2023-06-16  9:39 ` [PATCH v13 05/22] kvm/vfio: Accept vfio device file from userspace Yi Liu
2023-06-16  9:39 ` [PATCH v13 06/22] vfio: Pass struct vfio_device_file * to vfio_device_open/close() Yi Liu
2023-06-16  9:39 ` [PATCH v13 07/22] vfio: Block device access via device fd until device is opened Yi Liu
2023-06-16  9:39 ` [PATCH v13 08/22] vfio: Add cdev_device_open_cnt to vfio_group Yi Liu
2023-06-16  9:39 ` [PATCH v13 09/22] vfio: Make vfio_df_open() single open for device cdev path Yi Liu
2023-06-16  9:39 ` [PATCH v13 10/22] vfio-iommufd: Move noiommu compat validation out of vfio_iommufd_bind() Yi Liu
2023-06-16  9:39 ` [PATCH v13 11/22] vfio-iommufd: Split bind/attach into two steps Yi Liu
2023-06-16  9:39 ` [PATCH v13 12/22] vfio: Record devid in vfio_device_file Yi Liu
2023-06-16  9:39 ` [PATCH v13 13/22] vfio-iommufd: Add detach_ioas support for physical VFIO devices Yi Liu
2023-06-16  9:39 ` [PATCH v13 14/22] iommufd/device: Add iommufd_access_detach() API Yi Liu
2023-06-16  9:39 ` [PATCH v13 15/22] vfio-iommufd: Add detach_ioas support for emulated VFIO devices Yi Liu
2023-06-16  9:39 ` [PATCH v13 16/22] vfio: Move vfio_device_group_unregister() to be the first operation in unregister Yi Liu
2023-06-16  9:39 ` [PATCH v13 17/22] vfio: Add cdev for vfio_device Yi Liu
2023-06-16  9:39 ` [PATCH v13 18/22] vfio: Add VFIO_DEVICE_BIND_IOMMUFD Yi Liu
2023-06-16  9:39 ` [PATCH v13 19/22] vfio: Add VFIO_DEVICE_[AT|DE]TACH_IOMMUFD_PT Yi Liu
2023-06-16  9:39 ` [PATCH v13 20/22] vfio: Move the IOMMU_CAP_CACHE_COHERENCY check in __vfio_register_dev() Yi Liu
2023-06-16  9:39 ` [PATCH v13 21/22] vfio: Compile vfio_group infrastructure optionally Yi Liu
2023-07-17  6:36   ` Liu, Yi L
2023-07-17  8:08     ` Liu, Yi L
2023-07-17 18:45       ` Alex Williamson [this message]
2023-07-18  1:18         ` Liu, Yi L
2023-07-17 12:33     ` Jason Gunthorpe
2023-07-17 12:50       ` Liu, Yi L
2023-06-16  9:39 ` [PATCH v13 22/22] docs: vfio: Add vfio device cdev description Yi Liu
2023-06-21 21:54   ` Alex Williamson
2023-06-27  8:54     ` Liu, Yi L
2023-06-27 16:12       ` Jason Gunthorpe
2023-06-28  0:56         ` Liu, Yi L
2023-06-28 12:33           ` Jason Gunthorpe
     [not found]         ` <20230627113430.129811ef.alex.williamson@redhat.com>
2023-06-28  1:10           ` Liu, Yi L
2023-06-28 12:34             ` Jason Gunthorpe
2023-06-21  9:17 ` [PATCH v13 00/22] Add vfio_device cdev for iommufd support Duan, Zhenzhong
2023-06-23 16:48 ` Jason Gunthorpe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230717124539.743de027.alex.williamson@redhat.com \
    --to=alex.williamson@redhat.com \
    --cc=chao.p.peng@linux.intel.com \
    --cc=clegoate@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=eric.auger@redhat.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=jasowang@redhat.com \
    --cc=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=lulu@redhat.com \
    --cc=mjrosato@linux.ibm.com \
    --cc=nicolinc@nvidia.com \
    --cc=peterx@redhat.com \
    --cc=robin.murphy@arm.com \
    --cc=shameerali.kolothum.thodi@huawei.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=terrence.xu@intel.com \
    --cc=xudong.hao@intel.com \
    --cc=yan.y.zhao@intel.com \
    --cc=yanting.jiang@intel.com \
    --cc=yi.l.liu@intel.com \
    --cc=yi.y.sun@linux.intel.com \
    --cc=zhenzhong.duan@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox