search for: mmio_en

...r HVM guest, it will be killed obviously. 4) Trigger AER by test driver, an interrupt will be generated and caught by root port. 5) AER service driver below root port in DOM0 will help to do the recovery steps in bottom half of the aer interrupt context. For each recovery process (error_detected, mmio_enabled, slot_reset, error_resume), aer core will cooperate with each below devices which has registered pci_error_handlers to finish the process. For details, please see the related docs in kernel (attached aer_doc.patch). 6) pciback_error_handler will then be called by AER core for each above four p...

...ion 2: try to stop MMIO/config, resume on resume call Patch below implements Suggestion 1. Note that although this is really against the documentation, which states error_detected() is the point at which the driver should quiesce the device and not touch it further (until diagnostic poking at mmio_enabled or full access at resume callback). Fixing this won't be easy. However, this is not a regression. Also note this does nothing about interrupts, documentation suggests returning IRQ_NONE until reset. Again, not a regression. c. PF driver might detect that function is completely broken, if...

...ion 2: try to stop MMIO/config, resume on resume call Patch below implements Suggestion 1. Note that although this is really against the documentation, which states error_detected() is the point at which the driver should quiesce the device and not touch it further (until diagnostic poking at mmio_enabled or full access at resume callback). Fixing this won't be easy. However, this is not a regression. Also note this does nothing about interrupts, documentation suggests returning IRQ_NONE until reset. Again, not a regression. c. PF driver might detect that function is completely broken, if...

...ion 2: try to stop MMIO/config, resume on resume call Patch below implements Suggestion 1. Note that although this is really against the documentation, which states error_detected() is the point at which the driver should quiesce the device and not touch it further (until diagnostic poking at mmio_enabled or full access at resume callback). Fixing this won't be easy. However, this is not a regression. Also note this does nothing about interrupts, documentation suggests returning IRQ_NONE until reset. Again, not a regression. c. PF driver might detect that function is completely broken, if...

...ion 2: try to stop MMIO/config, resume on resume call Patch below implements Suggestion 1. Note that although this is really against the documentation, which states error_detected() is the point at which the driver should quiesce the device and not touch it further (until diagnostic poking at mmio_enabled or full access at resume callback). Fixing this won't be easy. However, this is not a regression. Also note this does nothing about interrupts, documentation suggests returning IRQ_NONE until reset. Again, not a regression. c. PF driver might detect that function is completely broken, if...

...de2 kernel: [ 1496.024193] pcieport > 0000:00:05.0: broadcast error_detected message > Mar 10 02:57:05 SunBlade2 kernel: [ 1496.024198] pciback 0000:0e:00.0: > pciback device is not found/assigned > Mar 10 02:57:05 SunBlade2 kernel: [ 1496.024201] pcieport > 0000:00:05.0: broadcast mmio_enabled message > Mar 10 02:57:05 SunBlade2 kernel: [ 1496.024203] pciback 0000:0e:00.0: > pciback device is not found/assigned > Mar 10 02:57:05 SunBlade2 kernel: [ 1496.024205] pcieport > 0000:00:05.0: broadcast resume message > Mar 10 02:57:05 SunBlade2 kernel: [ 1496.024208] pcib...

Hello, I''m hoping someone may be able to push us in the right direction. I''m trying to get one of our products to work with the current branch of Xen (4.0/4.0.0) but I''m hitting a problem. We are currently using Xen 3.3.2 on a Sun Blade 600 chassis (with x6270 blades) this works great. But when we upgrade to Xen 4.0/4.0.1 we get the following message when