search for: 4c1066

Displaying 7 results from an estimated 7 matches for "4c1066".

2013 Dec 17
2
[PATCH v4 RFC 0/3] virtio: add 'device_lost' to virtio_device
...ter at 44bbfa #29 [1e203ae0] css_sch_device_unregister at 4c06cc #30 [1e203b08] io_subchannel_sch_event at 4c8c3a #31 [1e203b80] css_evaluate_known_subchannel at 4c09bc #32 [1e203be0] slow_eval_known_fn at 4c19a6 #33 [1e203c10] bus_for_each_dev at 44d50e #34 [1e203c50] for_each_subchannel_staged at 4c1066 #35 [1e203c98] css_slow_path_func at 4c1124 #36 [1e203cc0] process_one_work at 16c7f6 #37 [1e203d60] worker_thread at 16dce4 #38 [1e203da8] kthread at 1786fc #39 [1e203eb0] kernel_thread_starter at 698fee Heinz > >> >> When an online channel device disappears on System z the kernel...
2013 Dec 17
2
[PATCH v4 RFC 0/3] virtio: add 'device_lost' to virtio_device
...ter at 44bbfa #29 [1e203ae0] css_sch_device_unregister at 4c06cc #30 [1e203b08] io_subchannel_sch_event at 4c8c3a #31 [1e203b80] css_evaluate_known_subchannel at 4c09bc #32 [1e203be0] slow_eval_known_fn at 4c19a6 #33 [1e203c10] bus_for_each_dev at 44d50e #34 [1e203c50] for_each_subchannel_staged at 4c1066 #35 [1e203c98] css_slow_path_func at 4c1124 #36 [1e203cc0] process_one_work at 16c7f6 #37 [1e203d60] worker_thread at 16dce4 #38 [1e203da8] kthread at 1786fc #39 [1e203eb0] kernel_thread_starter at 698fee Heinz > >> >> When an online channel device disappears on System z the kernel...
2013 Dec 23
2
[PATCH v4 RFC 0/3] virtio: add 'device_lost' to virtio_device
...nregister at 4c06cc >> #30 [1e203b08] io_subchannel_sch_event at 4c8c3a >> #31 [1e203b80] css_evaluate_known_subchannel at 4c09bc >> #32 [1e203be0] slow_eval_known_fn at 4c19a6 >> #33 [1e203c10] bus_for_each_dev at 44d50e >> #34 [1e203c50] for_each_subchannel_staged at 4c1066 >> #35 [1e203c98] css_slow_path_func at 4c1124 >> #36 [1e203cc0] process_one_work at 16c7f6 >> #37 [1e203d60] worker_thread at 16dce4 >> #38 [1e203da8] kthread at 1786fc >> #39 [1e203eb0] kernel_thread_starter at 698fee >> >> Heinz >> >>> &gt...
2013 Dec 23
2
[PATCH v4 RFC 0/3] virtio: add 'device_lost' to virtio_device
...nregister at 4c06cc >> #30 [1e203b08] io_subchannel_sch_event at 4c8c3a >> #31 [1e203b80] css_evaluate_known_subchannel at 4c09bc >> #32 [1e203be0] slow_eval_known_fn at 4c19a6 >> #33 [1e203c10] bus_for_each_dev at 44d50e >> #34 [1e203c50] for_each_subchannel_staged at 4c1066 >> #35 [1e203c98] css_slow_path_func at 4c1124 >> #36 [1e203cc0] process_one_work at 16c7f6 >> #37 [1e203d60] worker_thread at 16dce4 >> #38 [1e203da8] kthread at 1786fc >> #39 [1e203eb0] kernel_thread_starter at 698fee >> >> Heinz >> >>> &gt...
2013 Dec 19
0
[PATCH v4 RFC 0/3] virtio: add 'device_lost' to virtio_device
...e0] css_sch_device_unregister at 4c06cc > #30 [1e203b08] io_subchannel_sch_event at 4c8c3a > #31 [1e203b80] css_evaluate_known_subchannel at 4c09bc > #32 [1e203be0] slow_eval_known_fn at 4c19a6 > #33 [1e203c10] bus_for_each_dev at 44d50e > #34 [1e203c50] for_each_subchannel_staged at 4c1066 > #35 [1e203c98] css_slow_path_func at 4c1124 > #36 [1e203cc0] process_one_work at 16c7f6 > #37 [1e203d60] worker_thread at 16dce4 > #38 [1e203da8] kthread at 1786fc > #39 [1e203eb0] kernel_thread_starter at 698fee > > Heinz > >> >>> >>> When an onlin...
2013 Dec 13
7
[PATCH v4 RFC 0/3] virtio: add 'device_lost' to virtio_device
Hi, here is my v4 patch-set update to the v3 RFC submitted on Nov 27th. When an active virtio block device is hot-unplugged from a KVM guest, affected guest user applications are not aware of any errors that occur due to the lost device. This patch-set adds code to avoid further request queueing when a lost block device is detected, resulting in appropriate error info. Additionally a potential
2013 Dec 13
7
[PATCH v4 RFC 0/3] virtio: add 'device_lost' to virtio_device
Hi, here is my v4 patch-set update to the v3 RFC submitted on Nov 27th. When an active virtio block device is hot-unplugged from a KVM guest, affected guest user applications are not aware of any errors that occur due to the lost device. This patch-set adds code to avoid further request queueing when a lost block device is detected, resulting in appropriate error info. Additionally a potential