From: Jacob Pan <jacob.jun.pan@linux.intel.com> To: iommu@lists.linux-foundation.org, LKML <linux-kernel@vger.kernel.org>, Joerg Roedel <joro@8bytes.org>, David Woodhouse <dwmw2@infradead.org>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, Alex Williamson <alex.williamson@redhat.com>, Jean-Philippe Brucker <jean-philippe.brucker@arm.com> Cc: Rafael Wysocki <rafael.j.wysocki@intel.com>, "Liu, Yi L" <yi.l.liu@intel.com>, "Tian, Kevin" <kevin.tian@intel.com>, Raj Ashok <ashok.raj@intel.com>, Jean Delvare <khali@linux-fr.org>, "Christoph Hellwig" <hch@infradead.org>, "Lu Baolu" <baolu.lu@linux.intel.com>, Jacob Pan <jacob.jun.pan@linux.intel.com> Subject: [PATCH v4 14/22] iommu: handle page response timeout Date: Mon, 16 Apr 2018 14:49:03 -0700 [thread overview] Message-ID: <1523915351-54415-15-git-send-email-jacob.jun.pan@linux.intel.com> (raw) In-Reply-To: <1523915351-54415-1-git-send-email-jacob.jun.pan@linux.intel.com> When IO page faults are reported outside IOMMU subsystem, the page request handler may fail for various reasons. E.g. a guest received page requests but did not have a chance to run for a long time. The irresponsive behavior could hold off limited resources on the pending device. There can be hardware or credit based software solutions as suggested in the PCI ATS Ch-4. To provide a basic safty net this patch introduces a per device deferrable timer which monitors the longest pending page fault that requires a response. Proper action such as sending failure response code could be taken when timer expires but not included in this patch. We need to consider the life cycle of page groupd ID to prevent confusion with reused group ID by a device. For now, a warning message provides clue of such failure. Signed-off-by: Jacob Pan <jacob.jun.pan@linux.intel.com> Signed-off-by: Ashok Raj <ashok.raj@intel.com> --- drivers/iommu/iommu.c | 60 +++++++++++++++++++++++++++++++++++++++++++++++++-- include/linux/iommu.h | 4 ++++ 2 files changed, 62 insertions(+), 2 deletions(-) diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c index 628346c..f6512692 100644 --- a/drivers/iommu/iommu.c +++ b/drivers/iommu/iommu.c @@ -799,6 +799,39 @@ int iommu_group_unregister_notifier(struct iommu_group *group, } EXPORT_SYMBOL_GPL(iommu_group_unregister_notifier); +/* Max time to wait for a pending page request */ +#define IOMMU_PAGE_RESPONSE_MAXTIME (HZ * 10) +static void iommu_dev_fault_timer_fn(struct timer_list *t) +{ + struct iommu_fault_param *fparam = from_timer(fparam, t, timer); + struct iommu_fault_event *evt, *iter; + + u64 now; + + now = get_jiffies_64(); + + /* The goal is to ensure driver or guest page fault handler(via vfio) + * send page response on time. Otherwise, limited queue resources + * may be occupied by some irresponsive guests or drivers. + * When per device pending fault list is not empty, we periodically checks + * if any anticipated page response time has expired. + * + * TODO: + * We could do the following if response time expires: + * 1. send page response code FAILURE to all pending PRQ + * 2. inform device driver or vfio + * 3. drain in-flight page requests and responses for this device + * 4. clear pending fault list such that driver can unregister fault + * handler(otherwise blocked when pending faults are present). + */ + list_for_each_entry_safe(evt, iter, &fparam->faults, list) { + if (time_after64(evt->expire, now)) + pr_err("Page response time expired!, pasid %d gid %d exp %llu now %llu\n", + evt->pasid, evt->page_req_group_id, evt->expire, now); + } + mod_timer(t, now + IOMMU_PAGE_RESPONSE_MAXTIME); +} + /** * iommu_register_device_fault_handler() - Register a device fault handler * @dev: the device @@ -806,8 +839,8 @@ EXPORT_SYMBOL_GPL(iommu_group_unregister_notifier); * @data: private data passed as argument to the handler * * When an IOMMU fault event is received, call this handler with the fault event - * and data as argument. The handler should return 0. If the fault is - * recoverable (IOMMU_FAULT_PAGE_REQ), the handler must also complete + * and data as argument. The handler should return 0 on success. If the fault is + * recoverable (IOMMU_FAULT_PAGE_REQ), the handler can also complete * the fault by calling iommu_page_response() with one of the following * response code: * - IOMMU_PAGE_RESP_SUCCESS: retry the translation @@ -848,6 +881,9 @@ int iommu_register_device_fault_handler(struct device *dev, param->fault_param->data = data; INIT_LIST_HEAD(¶m->fault_param->faults); + timer_setup(¶m->fault_param->timer, iommu_dev_fault_timer_fn, + TIMER_DEFERRABLE); + mutex_unlock(¶m->lock); return 0; @@ -905,6 +941,8 @@ int iommu_report_device_fault(struct device *dev, struct iommu_fault_event *evt) { int ret = 0; struct iommu_fault_event *evt_pending; + struct timer_list *tmr; + u64 exp; struct iommu_fault_param *fparam; /* iommu_param is allocated when device is added to group */ @@ -925,6 +963,17 @@ int iommu_report_device_fault(struct device *dev, struct iommu_fault_event *evt) goto done_unlock; } memcpy(evt_pending, evt, sizeof(struct iommu_fault_event)); + /* Keep track of response expiration time */ + exp = get_jiffies_64() + IOMMU_PAGE_RESPONSE_MAXTIME; + evt_pending->expire = exp; + + if (list_empty(&fparam->faults)) { + /* First pending event, start timer */ + tmr = &dev->iommu_param->fault_param->timer; + WARN_ON(timer_pending(tmr)); + mod_timer(tmr, exp); + } + mutex_lock(&fparam->lock); list_add_tail(&evt_pending->list, &fparam->faults); mutex_unlock(&fparam->lock); @@ -1542,6 +1591,13 @@ int iommu_page_response(struct device *dev, } } + /* stop response timer if no more pending request */ + if (list_empty(¶m->fault_param->faults) && + timer_pending(¶m->fault_param->timer)) { + pr_debug("no pending PRQ, stop timer\n"); + del_timer(¶m->fault_param->timer); + } + done_unlock: mutex_unlock(¶m->fault_param->lock); return ret; diff --git a/include/linux/iommu.h b/include/linux/iommu.h index 058b552..40088d6 100644 --- a/include/linux/iommu.h +++ b/include/linux/iommu.h @@ -375,6 +375,7 @@ enum iommu_fault_reason { * @iommu_private: used by the IOMMU driver for storing fault-specific * data. Users should not modify this field before * sending the fault response. + * @expire: time limit in jiffies will wait for page response */ struct iommu_fault_event { struct list_head list; @@ -388,6 +389,7 @@ struct iommu_fault_event { u32 prot; u64 device_private; u64 iommu_private; + u64 expire; }; /** @@ -395,11 +397,13 @@ struct iommu_fault_event { * @dev_fault_handler: Callback function to handle IOMMU faults at device level * @data: handler private data * @faults: holds the pending faults which needs response, e.g. page response. + * @timer: track page request pending time limit * @lock: protect pending PRQ event list */ struct iommu_fault_param { iommu_dev_fault_handler_t handler; struct list_head faults; + struct timer_list timer; struct mutex lock; void *data; }; -- 2.7.4
WARNING: multiple messages have this Message-ID (diff)
From: Jacob Pan <jacob.jun.pan-VuQAYsv1563Yd54FQh9/CA@public.gmane.org> To: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>, David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>, Greg Kroah-Hartman <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>, Alex Williamson <alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>, Jean-Philippe Brucker <jean-philippe.brucker-5wv7dgnIgG8@public.gmane.org> Cc: Raj Ashok <ashok.raj-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>, Rafael Wysocki <rafael.j.wysocki-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>, Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org> Subject: [PATCH v4 14/22] iommu: handle page response timeout Date: Mon, 16 Apr 2018 14:49:03 -0700 [thread overview] Message-ID: <1523915351-54415-15-git-send-email-jacob.jun.pan@linux.intel.com> (raw) In-Reply-To: <1523915351-54415-1-git-send-email-jacob.jun.pan-VuQAYsv1563Yd54FQh9/CA@public.gmane.org> When IO page faults are reported outside IOMMU subsystem, the page request handler may fail for various reasons. E.g. a guest received page requests but did not have a chance to run for a long time. The irresponsive behavior could hold off limited resources on the pending device. There can be hardware or credit based software solutions as suggested in the PCI ATS Ch-4. To provide a basic safty net this patch introduces a per device deferrable timer which monitors the longest pending page fault that requires a response. Proper action such as sending failure response code could be taken when timer expires but not included in this patch. We need to consider the life cycle of page groupd ID to prevent confusion with reused group ID by a device. For now, a warning message provides clue of such failure. Signed-off-by: Jacob Pan <jacob.jun.pan-VuQAYsv1563Yd54FQh9/CA@public.gmane.org> Signed-off-by: Ashok Raj <ashok.raj-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> --- drivers/iommu/iommu.c | 60 +++++++++++++++++++++++++++++++++++++++++++++++++-- include/linux/iommu.h | 4 ++++ 2 files changed, 62 insertions(+), 2 deletions(-) diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c index 628346c..f6512692 100644 --- a/drivers/iommu/iommu.c +++ b/drivers/iommu/iommu.c @@ -799,6 +799,39 @@ int iommu_group_unregister_notifier(struct iommu_group *group, } EXPORT_SYMBOL_GPL(iommu_group_unregister_notifier); +/* Max time to wait for a pending page request */ +#define IOMMU_PAGE_RESPONSE_MAXTIME (HZ * 10) +static void iommu_dev_fault_timer_fn(struct timer_list *t) +{ + struct iommu_fault_param *fparam = from_timer(fparam, t, timer); + struct iommu_fault_event *evt, *iter; + + u64 now; + + now = get_jiffies_64(); + + /* The goal is to ensure driver or guest page fault handler(via vfio) + * send page response on time. Otherwise, limited queue resources + * may be occupied by some irresponsive guests or drivers. + * When per device pending fault list is not empty, we periodically checks + * if any anticipated page response time has expired. + * + * TODO: + * We could do the following if response time expires: + * 1. send page response code FAILURE to all pending PRQ + * 2. inform device driver or vfio + * 3. drain in-flight page requests and responses for this device + * 4. clear pending fault list such that driver can unregister fault + * handler(otherwise blocked when pending faults are present). + */ + list_for_each_entry_safe(evt, iter, &fparam->faults, list) { + if (time_after64(evt->expire, now)) + pr_err("Page response time expired!, pasid %d gid %d exp %llu now %llu\n", + evt->pasid, evt->page_req_group_id, evt->expire, now); + } + mod_timer(t, now + IOMMU_PAGE_RESPONSE_MAXTIME); +} + /** * iommu_register_device_fault_handler() - Register a device fault handler * @dev: the device @@ -806,8 +839,8 @@ EXPORT_SYMBOL_GPL(iommu_group_unregister_notifier); * @data: private data passed as argument to the handler * * When an IOMMU fault event is received, call this handler with the fault event - * and data as argument. The handler should return 0. If the fault is - * recoverable (IOMMU_FAULT_PAGE_REQ), the handler must also complete + * and data as argument. The handler should return 0 on success. If the fault is + * recoverable (IOMMU_FAULT_PAGE_REQ), the handler can also complete * the fault by calling iommu_page_response() with one of the following * response code: * - IOMMU_PAGE_RESP_SUCCESS: retry the translation @@ -848,6 +881,9 @@ int iommu_register_device_fault_handler(struct device *dev, param->fault_param->data = data; INIT_LIST_HEAD(¶m->fault_param->faults); + timer_setup(¶m->fault_param->timer, iommu_dev_fault_timer_fn, + TIMER_DEFERRABLE); + mutex_unlock(¶m->lock); return 0; @@ -905,6 +941,8 @@ int iommu_report_device_fault(struct device *dev, struct iommu_fault_event *evt) { int ret = 0; struct iommu_fault_event *evt_pending; + struct timer_list *tmr; + u64 exp; struct iommu_fault_param *fparam; /* iommu_param is allocated when device is added to group */ @@ -925,6 +963,17 @@ int iommu_report_device_fault(struct device *dev, struct iommu_fault_event *evt) goto done_unlock; } memcpy(evt_pending, evt, sizeof(struct iommu_fault_event)); + /* Keep track of response expiration time */ + exp = get_jiffies_64() + IOMMU_PAGE_RESPONSE_MAXTIME; + evt_pending->expire = exp; + + if (list_empty(&fparam->faults)) { + /* First pending event, start timer */ + tmr = &dev->iommu_param->fault_param->timer; + WARN_ON(timer_pending(tmr)); + mod_timer(tmr, exp); + } + mutex_lock(&fparam->lock); list_add_tail(&evt_pending->list, &fparam->faults); mutex_unlock(&fparam->lock); @@ -1542,6 +1591,13 @@ int iommu_page_response(struct device *dev, } } + /* stop response timer if no more pending request */ + if (list_empty(¶m->fault_param->faults) && + timer_pending(¶m->fault_param->timer)) { + pr_debug("no pending PRQ, stop timer\n"); + del_timer(¶m->fault_param->timer); + } + done_unlock: mutex_unlock(¶m->fault_param->lock); return ret; diff --git a/include/linux/iommu.h b/include/linux/iommu.h index 058b552..40088d6 100644 --- a/include/linux/iommu.h +++ b/include/linux/iommu.h @@ -375,6 +375,7 @@ enum iommu_fault_reason { * @iommu_private: used by the IOMMU driver for storing fault-specific * data. Users should not modify this field before * sending the fault response. + * @expire: time limit in jiffies will wait for page response */ struct iommu_fault_event { struct list_head list; @@ -388,6 +389,7 @@ struct iommu_fault_event { u32 prot; u64 device_private; u64 iommu_private; + u64 expire; }; /** @@ -395,11 +397,13 @@ struct iommu_fault_event { * @dev_fault_handler: Callback function to handle IOMMU faults at device level * @data: handler private data * @faults: holds the pending faults which needs response, e.g. page response. + * @timer: track page request pending time limit * @lock: protect pending PRQ event list */ struct iommu_fault_param { iommu_dev_fault_handler_t handler; struct list_head faults; + struct timer_list timer; struct mutex lock; void *data; }; -- 2.7.4
next prev parent reply other threads:[~2018-04-16 21:49 UTC|newest] Thread overview: 130+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-16 21:48 [PATCH v4 00/22] IOMMU and VT-d driver support for Shared Virtual Address (SVA) Jacob Pan 2018-04-16 21:48 ` Jacob Pan 2018-04-16 21:48 ` [PATCH v4 01/22] iommu: introduce bind_pasid_table API function Jacob Pan 2018-04-16 21:48 ` Jacob Pan 2018-04-16 21:48 ` [PATCH v4 02/22] iommu/vt-d: move device_domain_info to header Jacob Pan 2018-04-16 21:48 ` Jacob Pan 2018-04-16 21:48 ` [PATCH v4 03/22] iommu/vt-d: add a flag for pasid table bound status Jacob Pan 2018-04-16 21:48 ` Jacob Pan 2018-04-16 21:48 ` [PATCH v4 04/22] iommu/vt-d: add bind_pasid_table function Jacob Pan 2018-04-16 21:48 ` Jacob Pan 2018-04-17 19:10 ` Alex Williamson 2018-04-17 19:10 ` Alex Williamson 2018-04-20 18:25 ` Jean-Philippe Brucker 2018-04-20 18:25 ` Jean-Philippe Brucker 2018-04-20 23:42 ` Jacob Pan 2018-04-20 23:42 ` Jacob Pan 2018-05-29 20:09 ` Alex Williamson 2018-05-29 20:09 ` Alex Williamson 2018-05-30 1:41 ` Tian, Kevin 2018-05-30 1:41 ` Tian, Kevin 2018-05-30 3:17 ` Alex Williamson 2018-05-30 3:17 ` Alex Williamson 2018-05-30 3:45 ` Tian, Kevin 2018-05-30 3:45 ` Tian, Kevin 2018-05-30 11:53 ` Jean-Philippe Brucker 2018-05-30 11:53 ` Jean-Philippe Brucker 2018-05-30 19:52 ` Jacob Pan 2018-05-30 19:52 ` Jacob Pan 2018-05-31 9:09 ` Jean-Philippe Brucker 2018-05-31 9:09 ` Jean-Philippe Brucker 2018-06-05 17:32 ` Jacob Pan 2018-06-06 11:20 ` Jean-Philippe Brucker 2018-06-06 11:20 ` Jean-Philippe Brucker 2018-06-06 21:22 ` Jacob Pan 2018-06-07 13:21 ` Jean-Philippe Brucker 2018-04-20 23:22 ` Jacob Pan 2018-04-20 23:22 ` Jacob Pan 2018-04-16 21:48 ` [PATCH v4 05/22] iommu: introduce iommu invalidate API function Jacob Pan 2018-04-16 21:48 ` Jacob Pan 2018-04-20 18:19 ` Jean-Philippe Brucker 2018-04-20 18:19 ` Jean-Philippe Brucker 2018-04-23 20:43 ` Jacob Pan 2018-04-23 20:43 ` Jacob Pan 2018-04-27 18:07 ` Jean-Philippe Brucker 2018-04-27 18:07 ` Jean-Philippe Brucker 2018-04-28 2:41 ` Tian, Kevin 2018-04-28 2:41 ` Tian, Kevin 2018-05-01 22:58 ` Jacob Pan 2018-05-01 22:58 ` Jacob Pan 2018-05-02 9:31 ` Jean-Philippe Brucker 2018-05-02 9:31 ` Jean-Philippe Brucker 2018-05-04 4:46 ` Jacob Pan 2018-05-04 4:46 ` Jacob Pan 2018-05-04 18:07 ` Jacob Pan 2018-05-04 18:07 ` Jacob Pan 2018-05-08 10:35 ` Jean-Philippe Brucker 2018-05-08 10:35 ` Jean-Philippe Brucker 2018-05-09 12:55 ` Jacob Pan 2018-05-09 12:55 ` Jacob Pan 2018-05-05 22:19 ` Jerry Snitselaar 2018-05-05 22:19 ` Jerry Snitselaar 2018-05-07 15:41 ` Jacob Pan 2018-05-07 15:41 ` Jacob Pan 2018-04-16 21:48 ` [PATCH v4 06/22] iommu/vt-d: add definitions for PFSID Jacob Pan 2018-04-16 21:48 ` Jacob Pan 2018-04-16 21:48 ` [PATCH v4 07/22] iommu/vt-d: fix dev iotlb pfsid use Jacob Pan 2018-04-16 21:48 ` Jacob Pan 2018-04-16 21:48 ` [PATCH v4 08/22] iommu/vt-d: support flushing more translation cache types Jacob Pan 2018-04-16 21:48 ` Jacob Pan 2018-04-16 21:48 ` [PATCH v4 09/22] iommu/vt-d: add svm/sva invalidate function Jacob Pan 2018-04-16 21:48 ` Jacob Pan 2018-04-17 19:10 ` Alex Williamson 2018-04-17 19:10 ` Alex Williamson 2018-04-20 22:36 ` Jacob Pan 2018-04-20 22:36 ` Jacob Pan 2018-04-16 21:48 ` [PATCH v4 10/22] iommu: introduce device fault data Jacob Pan 2018-04-16 21:48 ` Jacob Pan 2018-04-23 10:11 ` Jean-Philippe Brucker 2018-04-23 10:11 ` Jean-Philippe Brucker 2018-04-23 11:54 ` Jacob Pan 2018-04-23 11:54 ` Jacob Pan 2018-05-20 8:17 ` Liu, Yi L 2018-05-21 23:16 ` Jacob Pan 2018-05-21 23:16 ` Jacob Pan 2018-04-16 21:49 ` [PATCH v4 11/22] driver core: add per device iommu param Jacob Pan 2018-04-16 21:49 ` Jacob Pan 2018-04-23 10:26 ` Greg Kroah-Hartman 2018-04-23 10:26 ` Greg Kroah-Hartman 2018-04-16 21:49 ` [PATCH v4 12/22] iommu: introduce device fault report API Jacob Pan 2018-04-16 21:49 ` Jacob Pan 2018-04-23 11:30 ` Jean-Philippe Brucker 2018-04-23 11:30 ` Jean-Philippe Brucker 2018-04-24 18:29 ` Jacob Pan 2018-04-24 18:29 ` Jacob Pan 2018-04-30 16:53 ` Jean-Philippe Brucker 2018-04-30 16:53 ` Jean-Philippe Brucker 2018-04-30 18:54 ` Jacob Pan 2018-04-16 21:49 ` [PATCH v4 13/22] iommu: introduce page response function Jacob Pan 2018-04-16 21:49 ` Jacob Pan 2018-04-23 11:47 ` Jean-Philippe Brucker 2018-04-23 11:47 ` Jean-Philippe Brucker 2018-04-23 12:16 ` Jacob Pan 2018-04-23 12:16 ` Jacob Pan 2018-04-23 15:50 ` Jean-Philippe Brucker 2018-04-23 15:50 ` Jean-Philippe Brucker 2018-04-16 21:49 ` Jacob Pan [this message] 2018-04-16 21:49 ` [PATCH v4 14/22] iommu: handle page response timeout Jacob Pan 2018-04-23 15:36 ` Jean-Philippe Brucker 2018-04-25 15:37 ` Jacob Pan 2018-04-25 15:37 ` Jacob Pan 2018-04-30 10:58 ` Jean-Philippe Brucker 2018-04-30 10:58 ` Jean-Philippe Brucker 2018-04-30 17:54 ` Jacob Pan 2018-04-30 17:54 ` Jacob Pan 2018-04-16 21:49 ` [PATCH v4 15/22] iommu/config: add build dependency for dmar Jacob Pan 2018-04-16 21:49 ` Jacob Pan 2018-04-16 21:49 ` [PATCH v4 16/22] iommu/vt-d: report non-recoverable faults to device Jacob Pan 2018-04-16 21:49 ` Jacob Pan 2018-04-16 21:49 ` [PATCH v4 17/22] iommu/intel-svm: report device page request Jacob Pan 2018-04-16 21:49 ` Jacob Pan 2018-04-16 21:49 ` [PATCH v4 18/22] iommu/intel-svm: replace dev ops with fault report API Jacob Pan 2018-04-16 21:49 ` Jacob Pan 2018-04-16 21:49 ` [PATCH v4 19/22] iommu/intel-svm: do not flush iotlb for viommu Jacob Pan 2018-04-16 21:49 ` Jacob Pan 2018-04-16 21:49 ` [PATCH v4 20/22] iommu/vt-d: add intel iommu page response function Jacob Pan 2018-04-16 21:49 ` Jacob Pan 2018-04-16 21:49 ` [PATCH v4 21/22] trace/iommu: add sva trace events Jacob Pan 2018-04-16 21:49 ` [PATCH v4 22/22] iommu: use sva invalidate and device fault trace event Jacob Pan -- strict thread matches above, loose matches on Subject: below -- 2018-03-23 3:11 [PATCH v4 00/22] IOMMU and VT-d driver support for Shared Virtual Address (SVA) Jacob Pan 2018-03-23 3:12 ` [PATCH v4 14/22] iommu: handle page response timeout Jacob Pan 2018-03-23 3:12 ` Jacob Pan
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=1523915351-54415-15-git-send-email-jacob.jun.pan@linux.intel.com \ --to=jacob.jun.pan@linux.intel.com \ --cc=alex.williamson@redhat.com \ --cc=ashok.raj@intel.com \ --cc=baolu.lu@linux.intel.com \ --cc=dwmw2@infradead.org \ --cc=gregkh@linuxfoundation.org \ --cc=hch@infradead.org \ --cc=iommu@lists.linux-foundation.org \ --cc=jean-philippe.brucker@arm.com \ --cc=joro@8bytes.org \ --cc=kevin.tian@intel.com \ --cc=khali@linux-fr.org \ --cc=linux-kernel@vger.kernel.org \ --cc=rafael.j.wysocki@intel.com \ --cc=yi.l.liu@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.