* [dpdk-dev] [PATCH 0/2] expose device states for hot-unplug
@ 2018-11-07 9:41 Jeff Guo
2018-11-07 9:41 ` [dpdk-dev] [PATCH 1/2] eal: expose device states in rte device Jeff Guo
2018-11-07 9:41 ` [dpdk-dev] [PATCH 2/2] but/pci: fix fd close for hot-unplug Jeff Guo
0 siblings, 2 replies; 9+ messages in thread
From: Jeff Guo @ 2018-11-07 9:41 UTC (permalink / raw)
To: ferruh.yigit, konstantin.ananyev, anatoly.burakov, thomas,
bernard.iremonger
Cc: dev, jia.guo, helin.zhang, stephen, gaetan.rivet, qi.z.zhang,
arybchenko, bruce.richardson, matan, shaopeng.he
Since the hotplug API and device event API have make public, so in order
to let applications or driver deal with device directly, it would be
helpful if the states of device could be exposed. Especially for hotplug
process, when device is hot-unplugged, some invalid process should be
skipped by checking the device status. It will avoid some error occur and
unnecessary loading.
So it is proposed that let eal framework take the control of device, it
provide device control APIs and device status checking. Something like
the rte_eth_dev_state for ethernet device could be delete later if it is
no specific usage and could be covered by the common rte device state.
Jeff Guo (2):
eal: expose device states in rte device
but/pci: fix fd close for hot-unplug
drivers/bus/pci/linux/pci_uio.c | 3 +++
drivers/bus/pci/pci_common_uio.c | 16 +++++++++-------
lib/librte_eal/common/include/rte_dev.h | 13 +++++++++++++
lib/librte_eal/linuxapp/eal/eal_dev.c | 1 +
4 files changed, 26 insertions(+), 7 deletions(-)
--
2.7.4
^ permalink raw reply [flat|nested] 9+ messages in thread
* [dpdk-dev] [PATCH 1/2] eal: expose device states in rte device
2018-11-07 9:41 [dpdk-dev] [PATCH 0/2] expose device states for hot-unplug Jeff Guo
@ 2018-11-07 9:41 ` Jeff Guo
2018-11-07 19:32 ` Stephen Hemminger
2018-11-07 9:41 ` [dpdk-dev] [PATCH 2/2] but/pci: fix fd close for hot-unplug Jeff Guo
1 sibling, 1 reply; 9+ messages in thread
From: Jeff Guo @ 2018-11-07 9:41 UTC (permalink / raw)
To: ferruh.yigit, konstantin.ananyev, anatoly.burakov, thomas,
bernard.iremonger
Cc: dev, jia.guo, helin.zhang, stephen, gaetan.rivet, qi.z.zhang,
arybchenko, bruce.richardson, matan, shaopeng.he
Since the hotplug API and device event API have make public, so in order
to let applications or driver deal with device directly, it would be
helpful if the states of device could be exposed, especially for hotplug
process.
This patch will add some devices states in rte device structure
to recode the device's current status, such as “RTE_DEV_UNUSED”,
“RTE_DEV_ATTACHED” and “RTE_DEV_REMOVED”.
Signed-off-by: Jeff Guo <jia.guo@intel.com>
---
lib/librte_eal/common/include/rte_dev.h | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/lib/librte_eal/common/include/rte_dev.h b/lib/librte_eal/common/include/rte_dev.h
index cd6c187..1bab0dd 100644
--- a/lib/librte_eal/common/include/rte_dev.h
+++ b/lib/librte_eal/common/include/rte_dev.h
@@ -151,6 +151,18 @@ struct rte_driver {
#define RTE_DEV_NAME_MAX_LEN 64
/**
+ * Possible states of an rte devcie.
+ */
+enum rte_dev_state {
+ /** Device is unused before being hotplug add. */
+ RTE_DEV_UNUSED = 0,
+ /** Device is attached when allocated in probing. */
+ RTE_DEV_ATTACHED,
+ /** Device is in removed state when plug-out is detected. */
+ RTE_DEV_REMOVED,
+};
+
+/**
* A structure describing a generic device.
*/
struct rte_device {
@@ -160,6 +172,7 @@ struct rte_device {
const struct rte_bus *bus; /**< Bus handle assigned on scan */
int numa_node; /**< NUMA node connection */
struct rte_devargs *devargs; /**< Arguments for latest probing */
+ enum rte_dev_state state; /**< Flag indicating the device state */
};
/**
--
2.7.4
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [dpdk-dev] [PATCH 1/2] eal: expose device states in rte device
2018-11-07 9:41 ` [dpdk-dev] [PATCH 1/2] eal: expose device states in rte device Jeff Guo
@ 2018-11-07 19:32 ` Stephen Hemminger
2018-11-09 7:35 ` Jeff Guo
0 siblings, 1 reply; 9+ messages in thread
From: Stephen Hemminger @ 2018-11-07 19:32 UTC (permalink / raw)
To: Jeff Guo
Cc: ferruh.yigit, konstantin.ananyev, anatoly.burakov, thomas,
bernard.iremonger, dev, helin.zhang, gaetan.rivet, qi.z.zhang,
arybchenko, bruce.richardson, matan, shaopeng.he
On Wed, 7 Nov 2018 17:41:30 +0800
Jeff Guo <jia.guo@intel.com> wrote:
> Since the hotplug API and device event API have make public, so in order
> to let applications or driver deal with device directly, it would be
> helpful if the states of device could be exposed, especially for hotplug
> process.
>
> This patch will add some devices states in rte device structure
> to recode the device's current status, such as “RTE_DEV_UNUSED”,
> “RTE_DEV_ATTACHED” and “RTE_DEV_REMOVED”.
>
> Signed-off-by: Jeff Guo <jia.guo@intel.com>
Looks good.
I did spot a couple of minor nits you might want to address if
resending this.
> ---
> lib/librte_eal/common/include/rte_dev.h | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/lib/librte_eal/common/include/rte_dev.h b/lib/librte_eal/common/include/rte_dev.h
> index cd6c187..1bab0dd 100644
> --- a/lib/librte_eal/common/include/rte_dev.h
> +++ b/lib/librte_eal/common/include/rte_dev.h
> @@ -151,6 +151,18 @@ struct rte_driver {
> #define RTE_DEV_NAME_MAX_LEN 64
>
> /**
> + * Possible states of an rte devcie.
> + */
s/devcie/device/
> +enum rte_dev_state {
> + /** Device is unused before being hotplug add. */
> + RTE_DEV_UNUSED = 0,
> + /** Device is attached when allocated in probing. */
> + RTE_DEV_ATTACHED,
> + /** Device is in removed state when plug-out is detected. */
> + RTE_DEV_REMOVED,
> +};
> +
> +/**
> * A structure describing a generic device.
> */
> struct rte_device {
> @@ -160,6 +172,7 @@ struct rte_device {
> const struct rte_bus *bus; /**< Bus handle assigned on scan */
> int numa_node; /**< NUMA node connection */
> struct rte_devargs *devargs; /**< Arguments for latest probing */
> + enum rte_dev_state state; /**< Flag indicating the device state */
Why not align comment with other fields here?
> };
>
> /**
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [dpdk-dev] [PATCH 1/2] eal: expose device states in rte device
2018-11-07 19:32 ` Stephen Hemminger
@ 2018-11-09 7:35 ` Jeff Guo
0 siblings, 0 replies; 9+ messages in thread
From: Jeff Guo @ 2018-11-09 7:35 UTC (permalink / raw)
To: Stephen Hemminger
Cc: ferruh.yigit, konstantin.ananyev, anatoly.burakov, thomas,
bernard.iremonger, dev, helin.zhang, gaetan.rivet, qi.z.zhang,
arybchenko, bruce.richardson, matan, shaopeng.he
On 11/8/2018 3:32 AM, Stephen Hemminger wrote:
> On Wed, 7 Nov 2018 17:41:30 +0800
> Jeff Guo <jia.guo@intel.com> wrote:
>
>> Since the hotplug API and device event API have make public, so in order
>> to let applications or driver deal with device directly, it would be
>> helpful if the states of device could be exposed, especially for hotplug
>> process.
>>
>> This patch will add some devices states in rte device structure
>> to recode the device's current status, such as “RTE_DEV_UNUSED”,
>> “RTE_DEV_ATTACHED” and “RTE_DEV_REMOVED”.
>>
>> Signed-off-by: Jeff Guo <jia.guo@intel.com>
> Looks good.
>
> I did spot a couple of minor nits you might want to address if
> resending this.
>
>
>> ---
>> lib/librte_eal/common/include/rte_dev.h | 13 +++++++++++++
>> 1 file changed, 13 insertions(+)
>>
>> diff --git a/lib/librte_eal/common/include/rte_dev.h b/lib/librte_eal/common/include/rte_dev.h
>> index cd6c187..1bab0dd 100644
>> --- a/lib/librte_eal/common/include/rte_dev.h
>> +++ b/lib/librte_eal/common/include/rte_dev.h
>> @@ -151,6 +151,18 @@ struct rte_driver {
>> #define RTE_DEV_NAME_MAX_LEN 64
>>
>> /**
>> + * Possible states of an rte devcie.
>> + */
> s/devcie/device/
got it.
>> +enum rte_dev_state {
>> + /** Device is unused before being hotplug add. */
>> + RTE_DEV_UNUSED = 0,
>> + /** Device is attached when allocated in probing. */
>> + RTE_DEV_ATTACHED,
>> + /** Device is in removed state when plug-out is detected. */
>> + RTE_DEV_REMOVED,
>> +};
>> +
>> +/**
>> * A structure describing a generic device.
>> */
>> struct rte_device {
>> @@ -160,6 +172,7 @@ struct rte_device {
>> const struct rte_bus *bus; /**< Bus handle assigned on scan */
>> int numa_node; /**< NUMA node connection */
>> struct rte_devargs *devargs; /**< Arguments for latest probing */
>> + enum rte_dev_state state; /**< Flag indicating the device state */
> Why not align comment with other fields here?
ok, maybe i could split the line if considerate with the line number limit.
>> };
>>
>> /**
^ permalink raw reply [flat|nested] 9+ messages in thread
* [dpdk-dev] [PATCH 2/2] but/pci: fix fd close for hot-unplug
2018-11-07 9:41 [dpdk-dev] [PATCH 0/2] expose device states for hot-unplug Jeff Guo
2018-11-07 9:41 ` [dpdk-dev] [PATCH 1/2] eal: expose device states in rte device Jeff Guo
@ 2018-11-07 9:41 ` Jeff Guo
2018-11-07 19:33 ` Stephen Hemminger
1 sibling, 1 reply; 9+ messages in thread
From: Jeff Guo @ 2018-11-07 9:41 UTC (permalink / raw)
To: ferruh.yigit, konstantin.ananyev, anatoly.burakov, thomas,
bernard.iremonger
Cc: dev, jia.guo, helin.zhang, stephen, gaetan.rivet, qi.z.zhang,
arybchenko, bruce.richardson, matan, shaopeng.he
When device is hot-unplugged, the device fd will be deleted in kernel.
Then in the progress of detaching device, if it try to close the fd,
it will cause a kernel crash, which shown a kernel null pointer error.
This patch aim to fix this issue by checking the device state to decide
whether the fd need to be closed or not.
Fixes: 5a60a7ffc801 ("pci: introduce functions to alloc and free uio resource")
Fixes: 9b957f378abf ("pci: merge uio functions for linux and bsd")
Fixes: 0fc54536b14a ("eal: add failure handling for hot-unplug")
Signed-off-by: Jeff Guo <jia.guo@intel.com>
---
drivers/bus/pci/linux/pci_uio.c | 3 +++
drivers/bus/pci/pci_common_uio.c | 16 +++++++++-------
lib/librte_eal/linuxapp/eal/eal_dev.c | 1 +
3 files changed, 13 insertions(+), 7 deletions(-)
diff --git a/drivers/bus/pci/linux/pci_uio.c b/drivers/bus/pci/linux/pci_uio.c
index a7c1442..7844ed4 100644
--- a/drivers/bus/pci/linux/pci_uio.c
+++ b/drivers/bus/pci/linux/pci_uio.c
@@ -199,6 +199,9 @@ pci_uio_free_resource(struct rte_pci_device *dev,
{
rte_free(uio_res);
+ if (dev->device.state == RTE_DEV_REMOVED)
+ return;
+
if (dev->intr_handle.uio_cfg_fd >= 0) {
close(dev->intr_handle.uio_cfg_fd);
dev->intr_handle.uio_cfg_fd = -1;
diff --git a/drivers/bus/pci/pci_common_uio.c b/drivers/bus/pci/pci_common_uio.c
index 7ea73db..bc329b5 100644
--- a/drivers/bus/pci/pci_common_uio.c
+++ b/drivers/bus/pci/pci_common_uio.c
@@ -227,12 +227,14 @@ pci_uio_unmap_resource(struct rte_pci_device *dev)
rte_free(uio_res);
/* close fd if in primary process */
- close(dev->intr_handle.fd);
- if (dev->intr_handle.uio_cfg_fd >= 0) {
- close(dev->intr_handle.uio_cfg_fd);
- dev->intr_handle.uio_cfg_fd = -1;
- }
+ if (dev->device.state != RTE_DEV_REMOVED && dev->intr_handle.fd >= 0) {
+ close(dev->intr_handle.fd);
+ if (dev->intr_handle.uio_cfg_fd >= 0) {
+ close(dev->intr_handle.uio_cfg_fd);
+ dev->intr_handle.uio_cfg_fd = -1;
+ }
- dev->intr_handle.fd = -1;
- dev->intr_handle.type = RTE_INTR_HANDLE_UNKNOWN;
+ dev->intr_handle.fd = -1;
+ dev->intr_handle.type = RTE_INTR_HANDLE_UNKNOWN;
+ }
}
diff --git a/lib/librte_eal/linuxapp/eal/eal_dev.c b/lib/librte_eal/linuxapp/eal/eal_dev.c
index 2830c86..030e639 100644
--- a/lib/librte_eal/linuxapp/eal/eal_dev.c
+++ b/lib/librte_eal/linuxapp/eal/eal_dev.c
@@ -269,6 +269,7 @@ dev_uev_handler(__rte_unused void *param)
goto failure_handle_err;
}
+ dev->state = RTE_DEV_REMOVED;
ret = bus->hot_unplug_handler(dev);
if (ret) {
RTE_LOG(ERR, EAL, "Can not handle hot-unplug "
--
2.7.4
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [dpdk-dev] [PATCH 2/2] but/pci: fix fd close for hot-unplug
2018-11-07 9:41 ` [dpdk-dev] [PATCH 2/2] but/pci: fix fd close for hot-unplug Jeff Guo
@ 2018-11-07 19:33 ` Stephen Hemminger
2018-11-08 3:10 ` Jeff Guo
0 siblings, 1 reply; 9+ messages in thread
From: Stephen Hemminger @ 2018-11-07 19:33 UTC (permalink / raw)
To: Jeff Guo
Cc: ferruh.yigit, konstantin.ananyev, anatoly.burakov, thomas,
bernard.iremonger, dev, helin.zhang, gaetan.rivet, qi.z.zhang,
arybchenko, bruce.richardson, matan, shaopeng.he
On Wed, 7 Nov 2018 17:41:31 +0800
Jeff Guo <jia.guo@intel.com> wrote:
> When device is hot-unplugged, the device fd will be deleted in kernel.
> Then in the progress of detaching device, if it try to close the fd,
> it will cause a kernel crash, which shown a kernel null pointer error.
If this happens, then it is a kernel bug and the kernel should be fixed.
Working around it in userspace is not a great long term solution.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [dpdk-dev] [PATCH 2/2] but/pci: fix fd close for hot-unplug
2018-11-07 19:33 ` Stephen Hemminger
@ 2018-11-08 3:10 ` Jeff Guo
2018-11-08 21:55 ` Stephen Hemminger
0 siblings, 1 reply; 9+ messages in thread
From: Jeff Guo @ 2018-11-08 3:10 UTC (permalink / raw)
To: Stephen Hemminger
Cc: ferruh.yigit, konstantin.ananyev, anatoly.burakov, thomas,
bernard.iremonger, dev, helin.zhang, gaetan.rivet, qi.z.zhang,
arybchenko, bruce.richardson, matan, shaopeng.he
hi, stephen
On 11/8/2018 3:33 AM, Stephen Hemminger wrote:
> On Wed, 7 Nov 2018 17:41:31 +0800
> Jeff Guo <jia.guo@intel.com> wrote:
>
>> When device is hot-unplugged, the device fd will be deleted in kernel.
>> Then in the progress of detaching device, if it try to close the fd,
>> it will cause a kernel crash, which shown a kernel null pointer error.
> If this happens, then it is a kernel bug and the kernel should be fixed.
> Working around it in userspace is not a great long term solution.
agree with you. The key is sometime hold by kernel. But i think it is at
least reasonable for avoiding no-use process in user space, whatever
kernel's behavior. I am not sure if there is any better idea we can
find, but seems it is an option now.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [dpdk-dev] [PATCH 2/2] but/pci: fix fd close for hot-unplug
2018-11-08 3:10 ` Jeff Guo
@ 2018-11-08 21:55 ` Stephen Hemminger
2018-11-09 3:26 ` Jeff Guo
0 siblings, 1 reply; 9+ messages in thread
From: Stephen Hemminger @ 2018-11-08 21:55 UTC (permalink / raw)
To: Jeff Guo
Cc: ferruh.yigit, konstantin.ananyev, anatoly.burakov, thomas,
bernard.iremonger, dev, helin.zhang, gaetan.rivet, qi.z.zhang,
arybchenko, bruce.richardson, matan, shaopeng.he
On Thu, 8 Nov 2018 11:10:29 +0800
Jeff Guo <jia.guo@intel.com> wrote:
> hi, stephen
>
> On 11/8/2018 3:33 AM, Stephen Hemminger wrote:
> > On Wed, 7 Nov 2018 17:41:31 +0800
> > Jeff Guo <jia.guo@intel.com> wrote:
> >
> >> When device is hot-unplugged, the device fd will be deleted in kernel.
> >> Then in the progress of detaching device, if it try to close the fd,
> >> it will cause a kernel crash, which shown a kernel null pointer error.
> > If this happens, then it is a kernel bug and the kernel should be fixed.
> > Working around it in userspace is not a great long term solution.
>
>
> agree with you. The key is sometime hold by kernel. But i think it is at
> least reasonable for avoiding no-use process in user space, whatever
> kernel's behavior. I am not sure if there is any better idea we can
> find, but seems it is an option now.
Are you using igb_uio? If so the problem is an DPDK supplied driver.
Let's fix that. What is the backtrace on kernel crash.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [dpdk-dev] [PATCH 2/2] but/pci: fix fd close for hot-unplug
2018-11-08 21:55 ` Stephen Hemminger
@ 2018-11-09 3:26 ` Jeff Guo
0 siblings, 0 replies; 9+ messages in thread
From: Jeff Guo @ 2018-11-09 3:26 UTC (permalink / raw)
To: Stephen Hemminger
Cc: ferruh.yigit, konstantin.ananyev, anatoly.burakov, thomas,
bernard.iremonger, dev, helin.zhang, gaetan.rivet, qi.z.zhang,
arybchenko, bruce.richardson, matan, shaopeng.he
On 11/9/2018 5:55 AM, Stephen Hemminger wrote:
> On Thu, 8 Nov 2018 11:10:29 +0800
> Jeff Guo <jia.guo@intel.com> wrote:
>
>> hi, stephen
>>
>> On 11/8/2018 3:33 AM, Stephen Hemminger wrote:
>>> On Wed, 7 Nov 2018 17:41:31 +0800
>>> Jeff Guo <jia.guo@intel.com> wrote:
>>>
>>>> When device is hot-unplugged, the device fd will be deleted in kernel.
>>>> Then in the progress of detaching device, if it try to close the fd,
>>>> it will cause a kernel crash, which shown a kernel null pointer error.
>>> If this happens, then it is a kernel bug and the kernel should be fixed.
>>> Working around it in userspace is not a great long term solution.
>>
>> agree with you. The key is sometime hold by kernel. But i think it is at
>> least reasonable for avoiding no-use process in user space, whatever
>> kernel's behavior. I am not sure if there is any better idea we can
>> find, but seems it is an option now.
> Are you using igb_uio? If so the problem is an DPDK supplied driver.
> Let's fix that. What is the backtrace on kernel crash.
yes, i am using the igb_uio. The back trace shown as below. It is an
kernel NULL pointer result of uio wirte error in the eal-intr-thread
thread,
################
[ 1052.262696] igb_uio 0000:00:03.0: mapping 1K dma=0x61cea000
host=ffff8e94e1cea000
[ 1052.262699] igb_uio 0000:00:03.0: unmapping 1K dma=0x61cea000
host=ffff8e94e1cea000
[ 1065.140839] igb_uio 0000:00:03.0: uio device registered with irq 24
[ 1078.006619] BUG: unable to handle kernel NULL pointer dereference at
00000000000001d0
[ 1078.006657] IP: uio_write+0x2e/0xc0 [uio]
[ 1078.006659] PGD 70837067
[ 1078.006659] PUD 3440c067
[ 1078.006660] PMD 0
[ 1078.006667] Oops: 0000 [#1] SMP
[ 1078.006677] Modules linked in: igb_uio(OE) uio sb_edac edac_core
kvm_intel kvm irqbypass crct10dif_pclmul joydev input_leds mac_hid
i2c_piix4 crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64
crypto_simd glue_helper cryptd serio_raw parport_pc ppdev lp parport
autofs4 8139too psmouse 8139cp ixgbevf mii pata_acpi floppy
[ 1078.006703] CPU: 3 PID: 14043 Comm: eal-intr-thread Tainted:
G OE 4.10.0-28-generic #32~16.04.2-Ubuntu
[ 1078.006705] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014
[ 1078.006706] task: ffff8e94f3904380 task.stack: ffffa97b810dc000
[ 1078.006709] RIP: 0010:uio_write+0x2e/0xc0 [uio]
[ 1078.006712] RSP: 0018:ffffa97b810dfe90 EFLAGS: 00010246
[ 1078.006714] RAX: 0000000000000000 RBX: 0000000000000004 RCX:
ffffa97b810dff18
[ 1078.006715] RDX: 0000000000000004 RSI: 00007f75a0c45294 RDI:
ffff8e94f3ff8d00
[ 1078.006716] RBP: ffffa97b810dfeb0 R08: ffffffffc01b6320 R09:
ffff8e94e1de9370
[ 1078.006717] R10: ffff8e94f3ff8d38 R11: ffff8e94f382f9c0 R12:
ffff8e94f2f94218
[ 1078.006718] R13: 00007f75a0c45294 R14: ffff8e94f3ff8d00 R15:
0000000000000000
[ 1078.006719] FS: 00007f75a0c47700(0000) GS:ffff8e95bfcc0000(0000)
knlGS:0000000000000000
[ 1078.006720] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1078.006721] CR2: 00000000000001d0 CR3: 0000000073abc000 CR4:
00000000001406e0
[ 1078.006727] Call Trace:
[ 1078.006765] __vfs_write+0x18/0x40
[ 1078.006768] vfs_write+0xb8/0x1b0
[ 1078.006770] SyS_write+0x55/0xc0
[ 1078.006791] entry_SYSCALL_64_fastpath+0x1e/0xad
[ 1078.006793] RIP: 0033:0x7f75a10224bd
[ 1078.006796] RSP: 002b:00007f75a0c45270 EFLAGS: 00003293 ORIG_RAX:
0000000000000001
[ 1078.006800] RAX: ffffffffffffffda RBX: 000000000000010c RCX:
00007f75a10224bd
[ 1078.006801] RDX: 0000000000000004 RSI: 00007f75a0c45294 RDI:
0000000000000010
[ 1078.006802] RBP: 00007f75a0c45250 R08: 00000000000010ed R09:
00000000010922e7
[ 1078.006803] R10: 0000000001777781 R11: 0000000000003293 R12:
00007f75a0c45680
[ 1078.006804] R13: 00007fff9036bb4f R14: 00007f75a0c479c0 R15:
0000000000000000
[ 1078.006805] Code: 00 00 55 48 89 e5 41 54 53 48 83 ec 10 65 48 8b 04
25 28 00 00 00 48 89 45 e8 31 c0 48 8b 87 c8 00 00 00 4c 8b 20 49 8b 44
24 38 <48> 83 b8 d0 01 00 00 00 74 6a 48 89 d3 48 c7 c2 ea ff ff ff 48
[ 1078.006832] RIP: uio_write+0x2e/0xc0 [uio] RSP: ffffa97b810dfe90
[ 1078.006832] CR2: 00000000000001d0
[ 1078.006837] ---[ end trace 88c298c83fcf2c2d ]---
#######
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2018-11-09 7:35 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-11-07 9:41 [dpdk-dev] [PATCH 0/2] expose device states for hot-unplug Jeff Guo
2018-11-07 9:41 ` [dpdk-dev] [PATCH 1/2] eal: expose device states in rte device Jeff Guo
2018-11-07 19:32 ` Stephen Hemminger
2018-11-09 7:35 ` Jeff Guo
2018-11-07 9:41 ` [dpdk-dev] [PATCH 2/2] but/pci: fix fd close for hot-unplug Jeff Guo
2018-11-07 19:33 ` Stephen Hemminger
2018-11-08 3:10 ` Jeff Guo
2018-11-08 21:55 ` Stephen Hemminger
2018-11-09 3:26 ` Jeff Guo
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).