unfair servicing of DomU vbd requests

unfair servicing of DomU vbd requests

[James Harper]

A user of GPLPV (see thread "blue screen in windows balloon driver") is
getting a bug check in Windows under extremely high memory usage and
swapfile thrashing tests across multiple DomU's. Responses to my query
on the ntdev mailing list say that this would happen if an IO request is
not completed after 70 seconds during high memory/pagefile pressure,
which is what is happening.

It appears that Dom0 is not servicing vbd requests from DomU's fairly so
one or two end up getting stalled while the others are mostly okay. How
are vbd requests supposed to be serviced? Is there potential for one to
be overlooked for a long period of time? Is there some settings that
could be changed to avoid this happening?

Thanks

James

Re: unfair servicing of DomU vbd requests

[Keir Fraser]

On 03/03/2011 02:25, "James Harper" <james.harper@bendigoit.com.au> wrote:

> A user of GPLPV (see thread "blue screen in windows balloon driver") is
> getting a bug check in Windows under extremely high memory usage and
> swapfile thrashing tests across multiple DomU's. Responses to my query
> on the ntdev mailing list say that this would happen if an IO request is
> not completed after 70 seconds during high memory/pagefile pressure,
> which is what is happening.
> 
> It appears that Dom0 is not servicing vbd requests from DomU's fairly so
> one or two end up getting stalled while the others are mostly okay. How
> are vbd requests supposed to be serviced? Is there potential for one to
> be overlooked for a long period of time? Is there some settings that
> could be changed to avoid this happening?

Dom0 does round-robin scanning of pending event channels these days, which
helps fairness a fair bit. When a pending event is found, the corresponding
blkfront has a batch of requests pulled down and submitted into Linux's
block subsystem at which point we have no more control over scheduling (it
could generally be configured though -- Linux has an admin mechanism for
that).

 -- Keir

> Thanks
> 
> James
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: unfair servicing of DomU vbd requests

[Ian Campbell]

On Thu, 2011-03-03 at 07:29 +0000, Keir Fraser wrote:
> On 03/03/2011 02:25, "James Harper" <james.harper@bendigoit.com.au> wrote:
> 
> > A user of GPLPV (see thread "blue screen in windows balloon driver") is
> > getting a bug check in Windows under extremely high memory usage and
> > swapfile thrashing tests across multiple DomU's. Responses to my query
> > on the ntdev mailing list say that this would happen if an IO request is
> > not completed after 70 seconds during high memory/pagefile pressure,
> > which is what is happening.
> > 
> > It appears that Dom0 is not servicing vbd requests from DomU's fairly so
> > one or two end up getting stalled while the others are mostly okay. How
> > are vbd requests supposed to be serviced? Is there potential for one to
> > be overlooked for a long period of time? Is there some settings that
> > could be changed to avoid this happening?
> 
> Dom0 does round-robin scanning of pending event channels these days, which
> helps fairness a fair bit.

I have a feeling this isn't true of pvops kernels...

looks like we need to pull 324:7fe1c6d02a2b (and subsequent fixes) out
of 2.6.18-xen.hg into the pvops world.

I'll take a look shortly if no one beats me to it.

>  When a pending event is found, the corresponding
> blkfront has a batch of requests pulled down and submitted into Linux's
> block subsystem at which point we have no more control over scheduling (it
> could generally be configured though -- Linux has an admin mechanism for
> that).
> 
>  -- Keir
> 
> > Thanks
> > 
> > James
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

RE: unfair servicing of DomU vbd requests

[James Harper]

[-- Attachment #1: Type: text/plain, Size: 866 bytes --]

> > > It appears that Dom0 is not servicing vbd requests from DomU's fairly so
> > > one or two end up getting stalled while the others are mostly okay. How
> > > are vbd requests supposed to be serviced? Is there potential for one to
> > > be overlooked for a long period of time? Is there some settings that
> > > could be changed to avoid this happening?
> >
> > Dom0 does round-robin scanning of pending event channels these days, which
> > helps fairness a fair bit.
> 
> I have a feeling this isn't true of pvops kernels...
> 
> looks like we need to pull 324:7fe1c6d02a2b (and subsequent fixes) out
> of 2.6.18-xen.hg into the pvops world.
> 

I hope that's true and easy to fix. It would certainly explain why one DomU can starve enough to the point where it's IO doesn't get serviced for >70 seconds.

Thanks for looking at this.

James

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: unfair servicing of DomU vbd requests

[Keir Fraser]

On 03/03/2011 08:28, "James Harper" <james.harper@bendigoit.com.au> wrote:

>>>> It appears that Dom0 is not servicing vbd requests from DomU's fairly so
>>>> one or two end up getting stalled while the others are mostly okay. How
>>>> are vbd requests supposed to be serviced? Is there potential for one to
>>>> be overlooked for a long period of time? Is there some settings that
>>>> could be changed to avoid this happening?
>>> 
>>> Dom0 does round-robin scanning of pending event channels these days, which
>>> helps fairness a fair bit.
>> 
>> I have a feeling this isn't true of pvops kernels...
>> 
>> looks like we need to pull 324:7fe1c6d02a2b (and subsequent fixes) out
>> of 2.6.18-xen.hg into the pvops world.
>> 
> 
> I hope that's true and easy to fix. It would certainly explain why one DomU
> can starve enough to the point where it's IO doesn't get serviced for >70
> seconds.

Without the round-robin servicing, unfairness to the point of starvation is
a distinct possibility.

 -- Keir

> Thanks for looking at this.
> 
> James

[GIT/PATCH 0/5] Re: unfair servicing of DomU vbd requests

[Ian Campbell]

On Thu, 2011-03-03 at 08:30 +0000, Keir Fraser wrote: 
> Without the round-robin servicing, unfairness to the point of starvation is
> a distinct possibility.

Indeed. The following is a forward port of these patches from
2.6.18-xen.hg: 
      * 324:7fe1c6d02a2b 
      * 325:b2768401db94 
      * 988:c88a02a22a05 
      * 990:427276ac595d 
      * 991:9ba6d9f3fbc0

Hopefully I didn't miss any.

The switch in pvops from "l1"/"l2" naming convention to "word"/"bit"
made the conflict resolution a bit prone to thinkos but hopefully I
didn't b0rk it too badly. Review with that in mind greatly appreciated.

boots a dom0 + a pv guest.

Pull request on top of konrad/stable/irq.cleanup:

The following changes since commit c5ae07bb307b658c8458f29ca77d237aec0f9327:
  Ian Campbell (1):
        xen: events: remove dom0 specific xen_create_msi_irq

are available in the git repository at:

  git://xenbits.xen.org/people/ianc/linux-2.6.git irq-fairness

Ian Campbell (1):
      xen: events: Make last processed event channel a per-cpu variable.

Keir Fraser (3):
      xen: events: Clean up round-robin evtchn scan.
      xen: events: Make round-robin scan fairer by snapshotting each l2 word
      xen: events: Remove redundant clear of l2i at end of round-robin loop

Scott Rixner (1):
      xen: events: Process event channels notifications in round-robin order.

 drivers/xen/events.c |   80 +++++++++++++++++++++++++++++++++++++++++++++-----
 1 files changed, 72 insertions(+), 8 deletions(-)



Ian.

[PATCH 1/5] xen: events: Process event channels notifications in round-robin order.

[Ian Campbell]

From: Scott Rixner <rixner@rice.edu>

Avoids fairness issue resulting from domain 0 processing lowest
numbered event channel first.

Bugzilla #1115 "Event channel port scanning unfair".

Signed-off-by: Ian Campbell <ian.campbell@xensource.com>
Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
[ijc: forward ported from linux-2.6.18-xen.hg 324:7fe1c6d02a2b
 various variables have different names in this tree:
  l1  -> pending_words
  l2  -> pending_bits
  l1i -> word_idx
  l2i -> bit_idx
]
---
 drivers/xen/events.c |   72 +++++++++++++++++++++++++++++++++++++++++++++-----
 1 files changed, 65 insertions(+), 7 deletions(-)

diff --git a/drivers/xen/events.c b/drivers/xen/events.c
index 6befe62..75cc6f5 100644
--- a/drivers/xen/events.c
+++ b/drivers/xen/events.c
@@ -1028,6 +1028,11 @@ irqreturn_t xen_debug_interrupt(int irq, void *dev_id)
 static DEFINE_PER_CPU(unsigned, xed_nesting_count);
 
 /*
+ * Mask out the i least significant bits of w
+ */
+#define MASK_LSBS(w, i) (w & ((~0UL) << i))
+
+/*
  * Search the CPUs pending events bitmasks.  For each one found, map
  * the event number to an irq, and feed it into do_IRQ() for
  * handling.
@@ -1038,6 +1043,9 @@ static DEFINE_PER_CPU(unsigned, xed_nesting_count);
  */
 static void __xen_evtchn_do_upcall(void)
 {
+	static unsigned int last_word_idx = BITS_PER_LONG - 1;
+	static unsigned int last_bit_idx = BITS_PER_LONG - 1;
+	int word_idx, bit_idx;
 	int cpu = get_cpu();
 	struct shared_info *s = HYPERVISOR_shared_info;
 	struct vcpu_info *vcpu_info = __this_cpu_read(xen_vcpu);
@@ -1056,17 +1064,50 @@ static void __xen_evtchn_do_upcall(void)
 		wmb();
 #endif
 		pending_words = xchg(&vcpu_info->evtchn_pending_sel, 0);
+
+		word_idx = last_word_idx;
+		bit_idx = last_bit_idx;
+
 		while (pending_words != 0) {
 			unsigned long pending_bits;
-			int word_idx = __ffs(pending_words);
-			pending_words &= ~(1UL << word_idx);
+			unsigned long words;
+
+			word_idx = (word_idx + 1) % BITS_PER_LONG;
+			words = MASK_LSBS(pending_words, word_idx);
+
+			/*
+			 * If we masked out all events, wrap around to the
+			 * beginning.
+			 */
+			if (words == 0) {
+				word_idx = BITS_PER_LONG - 1;
+				bit_idx = BITS_PER_LONG - 1;
+				continue;
+			}
+			word_idx = __ffs(words);
 
-			while ((pending_bits = active_evtchns(cpu, s, word_idx)) != 0) {
-				int bit_idx = __ffs(pending_bits);
-				int port = (word_idx * BITS_PER_LONG) + bit_idx;
-				int irq = evtchn_to_irq[port];
+			do {
+				unsigned long bits;
+				int port, irq;
 				struct irq_desc *desc;
 
+				pending_bits = active_evtchns(cpu, s, word_idx);
+
+				bit_idx = (bit_idx + 1) % BITS_PER_LONG;
+				bits = MASK_LSBS(pending_bits, bit_idx);
+
+				/* If we masked out all events, move on. */
+				if (bits == 0) {
+					bit_idx = BITS_PER_LONG - 1;
+					break;
+				}
+
+				bit_idx = __ffs(bits);
+
+				/* Process port. */
+				port = (word_idx * BITS_PER_LONG) + bit_idx;
+				irq = evtchn_to_irq[port];
+
 				mask_evtchn(port);
 				clear_evtchn(port);
 
@@ -1075,7 +1116,24 @@ static void __xen_evtchn_do_upcall(void)
 					if (desc)
 						generic_handle_irq_desc(irq, desc);
 				}
-			}
+
+				/*
+				 * If this is the final port processed, we'll
+				 * pick up here+1 next time.
+				 */
+				last_word_idx = word_idx;
+				last_bit_idx = bit_idx;
+
+			} while (bit_idx != BITS_PER_LONG - 1);
+
+			pending_bits = active_evtchns(cpu, s, word_idx);
+
+			/*
+			 * We handled all ports, so we can clear the
+			 * selector bit.
+			 */
+			if (pending_bits == 0)
+				pending_words &= ~(1UL << word_idx);
 		}
 
 		BUG_ON(!irqs_disabled());
-- 
1.5.6.5

[PATCH 2/5] xen: events: Make last processed event channel a per-cpu variable.

[Ian Campbell]

Signed-off-by: Ian Campbell <ian.campbell@xensource.com>
Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
[ijc: forward ported from linux-2.6.18-xen.hg 325:b2768401db94]
---
 drivers/xen/events.c |   13 ++++++-------
 1 files changed, 6 insertions(+), 7 deletions(-)

diff --git a/drivers/xen/events.c b/drivers/xen/events.c
index 75cc6f5..1fc3192 100644
--- a/drivers/xen/events.c
+++ b/drivers/xen/events.c
@@ -1026,6 +1026,8 @@ irqreturn_t xen_debug_interrupt(int irq, void *dev_id)
 }
 
 static DEFINE_PER_CPU(unsigned, xed_nesting_count);
+static DEFINE_PER_CPU(unsigned int, last_word_idx) = { BITS_PER_LONG - 1 };
+static DEFINE_PER_CPU(unsigned int, last_bit_idx) = { BITS_PER_LONG - 1 };
 
 /*
  * Mask out the i least significant bits of w
@@ -1043,8 +1045,6 @@ static DEFINE_PER_CPU(unsigned, xed_nesting_count);
  */
 static void __xen_evtchn_do_upcall(void)
 {
-	static unsigned int last_word_idx = BITS_PER_LONG - 1;
-	static unsigned int last_bit_idx = BITS_PER_LONG - 1;
 	int word_idx, bit_idx;
 	int cpu = get_cpu();
 	struct shared_info *s = HYPERVISOR_shared_info;
@@ -1065,8 +1065,8 @@ static void __xen_evtchn_do_upcall(void)
 #endif
 		pending_words = xchg(&vcpu_info->evtchn_pending_sel, 0);
 
-		word_idx = last_word_idx;
-		bit_idx = last_bit_idx;
+		word_idx = __this_cpu_read(last_word_idx);
+		bit_idx = __this_cpu_read(last_bit_idx);
 
 		while (pending_words != 0) {
 			unsigned long pending_bits;
@@ -1121,9 +1121,8 @@ static void __xen_evtchn_do_upcall(void)
 				 * If this is the final port processed, we'll
 				 * pick up here+1 next time.
 				 */
-				last_word_idx = word_idx;
-				last_bit_idx = bit_idx;
-
+				__this_cpu_write(last_word_idx, word_idx);
+				__this_cpu_write(last_bit_idx, bit_idx);
 			} while (bit_idx != BITS_PER_LONG - 1);
 
 			pending_bits = active_evtchns(cpu, s, word_idx);
-- 
1.5.6.5

Re: [PATCH 2/5] xen: events: Make last processed event channel a per-cpu variable.

[Konrad Rzeszutek Wilk]

On Thu, Mar 03, 2011 at 05:10:12PM +0000, Ian Campbell wrote:
> Signed-off-by: Ian Campbell <ian.campbell@xensource.com>
> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>

You cloned yourself?

> [ijc: forward ported from linux-2.6.18-xen.hg 325:b2768401db94]
> ---
>  drivers/xen/events.c |   13 ++++++-------
>  1 files changed, 6 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/xen/events.c b/drivers/xen/events.c
> index 75cc6f5..1fc3192 100644
> --- a/drivers/xen/events.c
> +++ b/drivers/xen/events.c
> @@ -1026,6 +1026,8 @@ irqreturn_t xen_debug_interrupt(int irq, void *dev_id)
>  }
>  
>  static DEFINE_PER_CPU(unsigned, xed_nesting_count);
> +static DEFINE_PER_CPU(unsigned int, last_word_idx) = { BITS_PER_LONG - 1 };
> +static DEFINE_PER_CPU(unsigned int, last_bit_idx) = { BITS_PER_LONG - 1 };
>  
>  /*
>   * Mask out the i least significant bits of w
> @@ -1043,8 +1045,6 @@ static DEFINE_PER_CPU(unsigned, xed_nesting_count);
>   */
>  static void __xen_evtchn_do_upcall(void)
>  {
> -	static unsigned int last_word_idx = BITS_PER_LONG - 1;
> -	static unsigned int last_bit_idx = BITS_PER_LONG - 1;
>  	int word_idx, bit_idx;
>  	int cpu = get_cpu();
>  	struct shared_info *s = HYPERVISOR_shared_info;
> @@ -1065,8 +1065,8 @@ static void __xen_evtchn_do_upcall(void)
>  #endif
>  		pending_words = xchg(&vcpu_info->evtchn_pending_sel, 0);
>  
> -		word_idx = last_word_idx;
> -		bit_idx = last_bit_idx;
> +		word_idx = __this_cpu_read(last_word_idx);
> +		bit_idx = __this_cpu_read(last_bit_idx);
>  
>  		while (pending_words != 0) {
>  			unsigned long pending_bits;
> @@ -1121,9 +1121,8 @@ static void __xen_evtchn_do_upcall(void)
>  				 * If this is the final port processed, we'll
>  				 * pick up here+1 next time.
>  				 */
> -				last_word_idx = word_idx;
> -				last_bit_idx = bit_idx;
> -
> +				__this_cpu_write(last_word_idx, word_idx);
> +				__this_cpu_write(last_bit_idx, bit_idx);
>  			} while (bit_idx != BITS_PER_LONG - 1);
>  
>  			pending_bits = active_evtchns(cpu, s, word_idx);
> -- 
> 1.5.6.5
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: [PATCH 2/5] xen: events: Make last processed event channel a per-cpu variable.

[Ian Campbell]

On Wed, 2011-03-09 at 20:32 +0000, Konrad Rzeszutek Wilk wrote:
> On Thu, Mar 03, 2011 at 05:10:12PM +0000, Ian Campbell wrote:
> > Signed-off-by: Ian Campbell <ian.campbell@xensource.com>
> > Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> 
> You cloned yourself?

The first is from the original linux-2.6.18-xen.hg commit.

The second is from today as I forward the change upstream.

I wasn't really sure what to do with the historical signed-off-by so I
decided to leave it, just as I would have done if it had been someone
else's.

Ian.

> 
> > [ijc: forward ported from linux-2.6.18-xen.hg 325:b2768401db94]
> > ---
> >  drivers/xen/events.c |   13 ++++++-------
> >  1 files changed, 6 insertions(+), 7 deletions(-)
> > 
> > diff --git a/drivers/xen/events.c b/drivers/xen/events.c
> > index 75cc6f5..1fc3192 100644
> > --- a/drivers/xen/events.c
> > +++ b/drivers/xen/events.c
> > @@ -1026,6 +1026,8 @@ irqreturn_t xen_debug_interrupt(int irq, void *dev_id)
> >  }
> >  
> >  static DEFINE_PER_CPU(unsigned, xed_nesting_count);
> > +static DEFINE_PER_CPU(unsigned int, last_word_idx) = { BITS_PER_LONG - 1 };
> > +static DEFINE_PER_CPU(unsigned int, last_bit_idx) = { BITS_PER_LONG - 1 };
> >  
> >  /*
> >   * Mask out the i least significant bits of w
> > @@ -1043,8 +1045,6 @@ static DEFINE_PER_CPU(unsigned, xed_nesting_count);
> >   */
> >  static void __xen_evtchn_do_upcall(void)
> >  {
> > -	static unsigned int last_word_idx = BITS_PER_LONG - 1;
> > -	static unsigned int last_bit_idx = BITS_PER_LONG - 1;
> >  	int word_idx, bit_idx;
> >  	int cpu = get_cpu();
> >  	struct shared_info *s = HYPERVISOR_shared_info;
> > @@ -1065,8 +1065,8 @@ static void __xen_evtchn_do_upcall(void)
> >  #endif
> >  		pending_words = xchg(&vcpu_info->evtchn_pending_sel, 0);
> >  
> > -		word_idx = last_word_idx;
> > -		bit_idx = last_bit_idx;
> > +		word_idx = __this_cpu_read(last_word_idx);
> > +		bit_idx = __this_cpu_read(last_bit_idx);
> >  
> >  		while (pending_words != 0) {
> >  			unsigned long pending_bits;
> > @@ -1121,9 +1121,8 @@ static void __xen_evtchn_do_upcall(void)
> >  				 * If this is the final port processed, we'll
> >  				 * pick up here+1 next time.
> >  				 */
> > -				last_word_idx = word_idx;
> > -				last_bit_idx = bit_idx;
> > -
> > +				__this_cpu_write(last_word_idx, word_idx);
> > +				__this_cpu_write(last_bit_idx, bit_idx);
> >  			} while (bit_idx != BITS_PER_LONG - 1);
> >  
> >  			pending_bits = active_evtchns(cpu, s, word_idx);
> > -- 
> > 1.5.6.5
> > 
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel

Re: [PATCH 2/5] xen: events: Make last processed event channel a per-cpu variable.

[Jeremy Fitzhardinge]

On 03/09/2011 12:40 PM, Ian Campbell wrote:
> On Wed, 2011-03-09 at 20:32 +0000, Konrad Rzeszutek Wilk wrote:
>> On Thu, Mar 03, 2011 at 05:10:12PM +0000, Ian Campbell wrote:
>>> Signed-off-by: Ian Campbell <ian.campbell@xensource.com>
>>> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
>> You cloned yourself?
> The first is from the original linux-2.6.18-xen.hg commit.
>
> The second is from today as I forward the change upstream.
>
> I wasn't really sure what to do with the historical signed-off-by so I
> decided to leave it, just as I would have done if it had been someone
> else's.

Since Citrix and Xensource are logically the same entity, just the
Citrix one should be fine.

    J

Re: [PATCH 2/5] xen: events: Make last processed event channel a per-cpu variable.

[Ian Campbell]

On Wed, 2011-03-09 at 20:47 +0000, Jeremy Fitzhardinge wrote:
> On 03/09/2011 12:40 PM, Ian Campbell wrote:
> > On Wed, 2011-03-09 at 20:32 +0000, Konrad Rzeszutek Wilk wrote:
> >> On Thu, Mar 03, 2011 at 05:10:12PM +0000, Ian Campbell wrote:
> >>> Signed-off-by: Ian Campbell <ian.campbell@xensource.com>
> >>> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> >> You cloned yourself?
> > The first is from the original linux-2.6.18-xen.hg commit.
> >
> > The second is from today as I forward the change upstream.
> >
> > I wasn't really sure what to do with the historical signed-off-by so I
> > decided to leave it, just as I would have done if it had been someone
> > else's.
> 
> Since Citrix and Xensource are logically the same entity, just the
> Citrix one should be fine.

You are almost certainly right, but the xensource one is harmless and
accurately describes the provenance of the patch.

More importantly I don't think it's a big enough deal to be worth
respinning the series

Ian.

Re: [PATCH 2/5] xen: events: Make last processed event channel a per-cpu variable.

[Jeremy Fitzhardinge]

On 03/10/2011 12:30 AM, Ian Campbell wrote:
> More importantly I don't think it's a big enough deal to be worth
> respinning the series

Definitely not.

    J

[PATCH 3/5] xen: events: Clean up round-robin evtchn scan.

[Ian Campbell]

From: Keir Fraser <keir.fraser@citrix.com>

Also fixes a couple of boundary cases.

Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
[ijc: forward ported from linux-2.6.18-xen.hg 988:c88a02a22a05]
---
 drivers/xen/events.c |   44 ++++++++++++++++++++------------------------
 1 files changed, 20 insertions(+), 24 deletions(-)

diff --git a/drivers/xen/events.c b/drivers/xen/events.c
index 1fc3192..c49cb6d 100644
--- a/drivers/xen/events.c
+++ b/drivers/xen/events.c
@@ -1026,8 +1026,8 @@ irqreturn_t xen_debug_interrupt(int irq, void *dev_id)
 }
 
 static DEFINE_PER_CPU(unsigned, xed_nesting_count);
-static DEFINE_PER_CPU(unsigned int, last_word_idx) = { BITS_PER_LONG - 1 };
-static DEFINE_PER_CPU(unsigned int, last_bit_idx) = { BITS_PER_LONG - 1 };
+static DEFINE_PER_CPU(unsigned int, current_word_idx);
+static DEFINE_PER_CPU(unsigned int, current_bit_idx);
 
 /*
  * Mask out the i least significant bits of w
@@ -1065,23 +1065,21 @@ static void __xen_evtchn_do_upcall(void)
 #endif
 		pending_words = xchg(&vcpu_info->evtchn_pending_sel, 0);
 
-		word_idx = __this_cpu_read(last_word_idx);
-		bit_idx = __this_cpu_read(last_bit_idx);
+		word_idx = __this_cpu_read(current_word_idx);
+		bit_idx = __this_cpu_read(current_bit_idx);
 
 		while (pending_words != 0) {
 			unsigned long pending_bits;
 			unsigned long words;
 
-			word_idx = (word_idx + 1) % BITS_PER_LONG;
 			words = MASK_LSBS(pending_words, word_idx);
 
 			/*
-			 * If we masked out all events, wrap around to the
-			 * beginning.
+			 * If we masked out all events, wrap to beginning.
 			 */
 			if (words == 0) {
-				word_idx = BITS_PER_LONG - 1;
-				bit_idx = BITS_PER_LONG - 1;
+				word_idx = 0;
+				bit_idx = 0;
 				continue;
 			}
 			word_idx = __ffs(words);
@@ -1093,14 +1091,11 @@ static void __xen_evtchn_do_upcall(void)
 
 				pending_bits = active_evtchns(cpu, s, word_idx);
 
-				bit_idx = (bit_idx + 1) % BITS_PER_LONG;
 				bits = MASK_LSBS(pending_bits, bit_idx);
 
 				/* If we masked out all events, move on. */
-				if (bits == 0) {
-					bit_idx = BITS_PER_LONG - 1;
+				if (bits == 0)
 					break;
-				}
 
 				bit_idx = __ffs(bits);
 
@@ -1117,22 +1112,23 @@ static void __xen_evtchn_do_upcall(void)
 						generic_handle_irq_desc(irq, desc);
 				}
 
-				/*
-				 * If this is the final port processed, we'll
-				 * pick up here+1 next time.
-				 */
-				__this_cpu_write(last_word_idx, word_idx);
-				__this_cpu_write(last_bit_idx, bit_idx);
-			} while (bit_idx != BITS_PER_LONG - 1);
+				bit_idx = (bit_idx + 1) % BITS_PER_LONG;
+
+				/* Next caller starts at last processed + 1 */
+				__this_cpu_write(current_word_idx,
+						 bit_idx ? word_idx :
+						 (word_idx+1) % BITS_PER_LONG);
+				__this_cpu_write(current_bit_idx, bit_idx);
+			} while (bit_idx != 0);
 
 			pending_bits = active_evtchns(cpu, s, word_idx);
 
-			/*
-			 * We handled all ports, so we can clear the
-			 * selector bit.
-			 */
+			/* If we handled all ports, clear the selector bit. */
 			if (pending_bits == 0)
 				pending_words &= ~(1UL << word_idx);
+
+			word_idx = (word_idx + 1) % BITS_PER_LONG;
+			bit_idx = 0;
 		}
 
 		BUG_ON(!irqs_disabled());
-- 
1.5.6.5

[PATCH 4/5] xen: events: Make round-robin scan fairer by snapshotting each l2 word

[Ian Campbell]

From: Keir Fraser <keir.fraser@citrix.com>

Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
[ijc: forward ported from linux-2.6.18-xen.hg 990:427276ac595d]
---
 drivers/xen/events.c |   30 +++++++++++++++++++++---------
 1 files changed, 21 insertions(+), 9 deletions(-)

diff --git a/drivers/xen/events.c b/drivers/xen/events.c
index c49cb6d..0c3f17b 100644
--- a/drivers/xen/events.c
+++ b/drivers/xen/events.c
@@ -1045,7 +1045,9 @@ static DEFINE_PER_CPU(unsigned int, current_bit_idx);
  */
 static void __xen_evtchn_do_upcall(void)
 {
+	int start_word_idx, start_bit_idx;
 	int word_idx, bit_idx;
+	int i;
 	int cpu = get_cpu();
 	struct shared_info *s = HYPERVISOR_shared_info;
 	struct vcpu_info *vcpu_info = __this_cpu_read(xen_vcpu);
@@ -1065,10 +1067,12 @@ static void __xen_evtchn_do_upcall(void)
 #endif
 		pending_words = xchg(&vcpu_info->evtchn_pending_sel, 0);
 
-		word_idx = __this_cpu_read(current_word_idx);
-		bit_idx = __this_cpu_read(current_bit_idx);
+		start_word_idx = __this_cpu_read(current_word_idx);
+		start_bit_idx = __this_cpu_read(current_bit_idx);
+
+		word_idx = start_word_idx;
 
-		while (pending_words != 0) {
+		for (i = 0; pending_words != 0; i++) {
 			unsigned long pending_bits;
 			unsigned long words;
 
@@ -1084,13 +1088,23 @@ static void __xen_evtchn_do_upcall(void)
 			}
 			word_idx = __ffs(words);
 
+			pending_bits = active_evtchns(cpu, s, word_idx);
+			bit_idx = 0; /* usually scan entire word from start */
+			if (word_idx == start_word_idx) {
+				/* We scan the starting word in two parts */
+				if (i == 0)
+					/* 1st time: start in the middle */
+					bit_idx = start_bit_idx;
+				else
+					/* 2nd time: mask bits done already */
+					bit_idx &= (1UL << start_bit_idx) - 1;
+			}
+
 			do {
 				unsigned long bits;
 				int port, irq;
 				struct irq_desc *desc;
 
-				pending_bits = active_evtchns(cpu, s, word_idx);
-
 				bits = MASK_LSBS(pending_bits, bit_idx);
 
 				/* If we masked out all events, move on. */
@@ -1121,10 +1135,8 @@ static void __xen_evtchn_do_upcall(void)
 				__this_cpu_write(current_bit_idx, bit_idx);
 			} while (bit_idx != 0);
 
-			pending_bits = active_evtchns(cpu, s, word_idx);
-
-			/* If we handled all ports, clear the selector bit. */
-			if (pending_bits == 0)
+			/* Scan start_l1i twice; all others once. */
+			if ((word_idx != start_word_idx) || (i != 0))
 				pending_words &= ~(1UL << word_idx);
 
 			word_idx = (word_idx + 1) % BITS_PER_LONG;
-- 
1.5.6.5

[PATCH 5/5] xen: events: Remove redundant clear of l2i at end of round-robin loop

[Ian Campbell]

From: Keir Fraser <keir.fraser@citrix.com>

Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
[ijc: forward ported from linux-2.6.18-xen.hg 991:9ba6d9f3fbc0]
---
 drivers/xen/events.c |    1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/drivers/xen/events.c b/drivers/xen/events.c
index 0c3f17b..8786e06 100644
--- a/drivers/xen/events.c
+++ b/drivers/xen/events.c
@@ -1140,7 +1140,6 @@ static void __xen_evtchn_do_upcall(void)
 				pending_words &= ~(1UL << word_idx);
 
 			word_idx = (word_idx + 1) % BITS_PER_LONG;
-			bit_idx = 0;
 		}
 
 		BUG_ON(!irqs_disabled());
-- 
1.5.6.5

Re: [GIT/PATCH 0/5] Re: unfair servicing of DomU vbd requests

[John Weekes]

On 3/3/2011 9:09 AM, Ian Campbell wrote:
> On Thu, 2011-03-03 at 08:30 +0000, Keir Fraser wrote:
>> >  Without the round-robin servicing, unfairness to the point of starvation is
>> >  a distinct possibility.
> Indeed. The following is a forward port of these patches from
> 2.6.18-xen.hg:

Thanks for working on this, Ian.

I think that this has affected me several times, as I've noticed these 
symptoms before (heavy disk access by a few domains, followed by several 
Windows domUs mysteriously rebooting) -- as recently as Wednesday, in 
fact. The I/O from rebooting domUs, unfortunately, makes everything even 
worse, often leading to further Windows domUs crashing.

I look forward to this being merged into stable-2.6.32. In the meantime, 
I'll monkey around with git as you described and try to get a local 
version working. I'm itching to test it out, since this also might 
explain some of the occasional the longish disk delays that I see on 
machines with a medium I/O load (in which the dom0 still responds 
normally, but one of the domUs frequently stalls waiting for I/O).

-John

Re: [GIT/PATCH 0/5] Re: unfair servicing of DomU vbd requests

[Ian Campbell]

On Fri, 2011-03-04 at 08:40 +0000, John Weekes wrote:
> On 3/3/2011 9:09 AM, Ian Campbell wrote:
> > On Thu, 2011-03-03 at 08:30 +0000, Keir Fraser wrote:
> >> >  Without the round-robin servicing, unfairness to the point of starvation is
> >> >  a distinct possibility.
> > Indeed. The following is a forward port of these patches from
> > 2.6.18-xen.hg:
> 
> Thanks for working on this, Ian.
> 
> I think that this has affected me several times, as I've noticed these 
> symptoms before (heavy disk access by a few domains, followed by several 
> Windows domUs mysteriously rebooting) -- as recently as Wednesday, in 
> fact. The I/O from rebooting domUs, unfortunately, makes everything even 
> worse, often leading to further Windows domUs crashing.
> 
> I look forward to this being merged into stable-2.6.32. In the meantime, 
> I'll monkey around with git as you described and try to get a local 
> version working. I'm itching to test it out, since this also might 
> explain some of the occasional the longish disk delays that I see on 
> machines with a medium I/O load (in which the dom0 still responds 
> normally, but one of the domUs frequently stalls waiting for I/O).

This series was for more recent kernels. It seems to backport with
minimum fuss (switch from __this_cpu_(read|write) to __get_cpu_var).

I only compile tested this one file and haven't even booted it but the
result is available on top of xen.git xen/next-2.6.32 at:

The following changes since commit 892d2f052e979cf1916647c752b94cf62ec1c6dc:
  Jeremy Fitzhardinge (1):
        Merge commit 'v2.6.32.28' into xen/next-2.6.32

are available in the git repository at:

  git://xenbits.xen.org/people/ianc/linux-2.6.git irq-fairness-2.6.32

Ian Campbell (1):
      xen: events: Make last processed event channel a per-cpu variable.

Keir Fraser (3):
      xen: events: Clean up round-robin evtchn scan.
      xen: events: Make round-robin scan fairer by snapshotting each l2 word
      xen: events: Remove redundant clear of l2i at end of round-robin loop

Scott Rixner (1):
      xen: events: Process event channels notifications in round-robin order.

 drivers/xen/events.c |   80 +++++++++++++++++++++++++++++++++++++++++++++-----
 1 files changed, 72 insertions(+), 8 deletions(-)

Ian.

Re: [GIT/PATCH 0/5] Re: unfair servicing of DomU vbd requests

[John Weekes]

On 3/4/2011 1:15 AM, Ian Campbell wrote:
> This series was for more recent kernels. It seems to backport with
> minimum fuss (switch from __this_cpu_(read|write) to __get_cpu_var).
>
> I only compile tested this one file and haven't even booted it but the
> result is available on top of xen.git xen/next-2.6.32 at:
> ...
>    git://xenbits.xen.org/people/ianc/linux-2.6.git irq-fairness-2.6.32

Thanks for the rebase and for the earlier instructions on how to merge 
your git topic branch, which were clear and easy to follow.

I've have this code running on a lightly-used production machine right 
now with no problems observed so far. I will continue to monitor and 
roll it out to a higher-usage machine that has had problems without the 
RR bits within the next few days, if all goes well.

-John

RE: [GIT/PATCH 0/5] Re: unfair servicing of DomU vbd requests

[MaoXiaoyun]

[-- Attachment #1.1: Type: text/plain, Size: 3227 bytes --]


I've tried to clone, but confront this error,  did I do right?
Thanks.
 
# git clone git://xenbits.xen.org/people/ianc/linux-2.6.git irq-fairness
Initialized empty Git repository in /mnt/hchina/xmao/irq-fairness/.git/
remote: Counting objects: 1938158, done.
remote: Compressing objects: 100% (372904/372904), done.
remote: Total 1938158 (delta 1618172), reused 1867564 (delta 1547775)
Receiving objects: 100% (1938158/1938158), 468.31 MiB | 1.41 MiB/s, done.
Resolving deltas: 100% (1618172/1618172), done.
warning: remote HEAD refers to nonexistent ref, unable to checkout.

 
> Subject: FW: [GIT/PATCH 0/5] Re: [Xen-devel] unfair servicing of DomU vbd requests
> Date: Fri, 4 Mar 2011 09:26:44 +1100
> From: james.harper@bendigoit.com.au
> To: tinnycloud@hotmail.com
> 
> Ian has posted some patches to xen-devel. Can you apply them to your Dom0 kernel and see if they fix your i/o servicing problem?
> 
> As I understand it, without this patch Dom0 will service the lowest event channel first, so if there is always an io request on the lower channel the higher channels will never get serviced. A bad disk would aggravate this situation but isn't really the cause of it.
> 
> James
> 
> > -----Original Message-----
> > From: Ian Campbell [mailto:Ian.Campbell@citrix.com]
> > Sent: Friday, 4 March 2011 04:10
> > To: Keir Fraser
> > Cc: James Harper; xen devel; Konrad Rzeszutek Wilk; Jeremy Fitzhardinge
> > Subject: [GIT/PATCH 0/5] Re: [Xen-devel] unfair servicing of DomU vbd requests
> > 
> > On Thu, 2011-03-03 at 08:30 +0000, Keir Fraser wrote:
> > > Without the round-robin servicing, unfairness to the point of starvation is
> > > a distinct possibility.
> > 
> > Indeed. The following is a forward port of these patches from
> > 2.6.18-xen.hg:
> > * 324:7fe1c6d02a2b
> > * 325:b2768401db94
> > * 988:c88a02a22a05
> > * 990:427276ac595d
> > * 991:9ba6d9f3fbc0
> > 
> > Hopefully I didn't miss any.
> > 
> > The switch in pvops from "l1"/"l2" naming convention to "word"/"bit"
> > made the conflict resolution a bit prone to thinkos but hopefully I
> > didn't b0rk it too badly. Review with that in mind greatly appreciated.
> > 
> > boots a dom0 + a pv guest.
> > 
> > Pull request on top of konrad/stable/irq.cleanup:
> > 
> > The following changes since commit c5ae07bb307b658c8458f29ca77d237aec0f9327:
> > Ian Campbell (1):
> > xen: events: remove dom0 specific xen_create_msi_irq
> > 
> > are available in the git repository at:
> > 
> > git://xenbits.xen.org/people/ianc/linux-2.6.git irq-fairness
> > 
> > Ian Campbell (1):
> > xen: events: Make last processed event channel a per-cpu variable.
> > 
> > Keir Fraser (3):
> > xen: events: Clean up round-robin evtchn scan.
> > xen: events: Make round-robin scan fairer by snapshotting each l2 word
> > xen: events: Remove redundant clear of l2i at end of round-robin loop
> > 
> > Scott Rixner (1):
> > xen: events: Process event channels notifications in round-robin order.
> > 
> > drivers/xen/events.c | 80 +++++++++++++++++++++++++++++++++++++++++++++----
> > -
> > 1 files changed, 72 insertions(+), 8 deletions(-)
> > 
> > 
> > 
> > Ian.
> > 
> > 
> > 
> 
 		 	   		  

[-- Attachment #1.2: Type: text/html, Size: 4014 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

RE: [GIT/PATCH 0/5] Re: unfair servicing of DomU vbd requests

[Ian Campbell]

On Fri, 2011-03-04 at 07:12 +0000, MaoXiaoyun wrote:
> I've tried to clone, but confront this error,  did I do right?

Your command will try and clone my default branch, which I'm not sure I
have configured (I don't really want one since no branch is particularly
special in my tree).

I would recommend that instead of completely cloning a fresh tree for
each tree you are interested in that you just add a new remote to your
existing tree, which could be a clone of e..g xen.git or Linus' tree.

e.g:

Once:
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
$ cd linux-2.6

Then for each new tree you are interested in:
linux-2.6$ git remote add ianc git://xenbits.xen.org/people/ianc/linux-2.6.git
linux-2.6$ git fetch ianc
[...pulls in updates from ianc...]
linux-2.6$ git log ianc/irq-fairness

etc. See "git remote --help" for more info.

Since my irq-fairness branch likely doesn't stand alone you will
probably need to merge it into your current 2.6.38 based head (something
like Konrad's 2.6.38 branch for example). e.g.

linux-2.6$ git merge ianc/irq-fairness

Alternatively (and better) you can pull a single remote branch and merge
it into your current head. e.g.
linux-2.6$ git pull git://xenbits.xen.org/people/ianc/linux-2.6.git irq-fairness

Compared with the git merge approach this creates a more informative
automated merge commit log.

The arguments to git pull are taken literally from the pull request:
> > > The following changes since commit c5ae07bb307b658c8458f29ca77d237aec0f9327:
> > > Ian Campbell (1):
> > > xen: events: remove dom0 specific xen_create_msi_irq
> > > 
> > > are available in the git repository at:
> > > 
> > > git://xenbits.xen.org/people/ianc/linux-2.6.git irq-fairness

Ian.

RE: [GIT/PATCH 0/5] Re: unfair servicing of DomU vbd requests

[MaoXiaoyun]

[-- Attachment #1.1: Type: text/plain, Size: 2381 bytes --]



Thanks Ian.
 
I've just pull the code.
But could the kernel be used as dom0, since I can't find blkback in driver/xen
which is needed, right?
 
And what is the usage of this branch?
 
 
> Subject: RE: [GIT/PATCH 0/5] Re: [Xen-devel] unfair servicing of DomU vbd requests
> From: Ian.Campbell@eu.citrix.com
> To: tinnycloud@hotmail.com
> CC: xen-devel@lists.xensource.com; james.harper@bendigoit.com.au
> Date: Fri, 4 Mar 2011 07:21:29 +0000
> 
> On Fri, 2011-03-04 at 07:12 +0000, MaoXiaoyun wrote:
> > I've tried to clone, but confront this error, did I do right?
> 
> Your command will try and clone my default branch, which I'm not sure I
> have configured (I don't really want one since no branch is particularly
> special in my tree).
> 
> I would recommend that instead of completely cloning a fresh tree for
> each tree you are interested in that you just add a new remote to your
> existing tree, which could be a clone of e..g xen.git or Linus' tree.
> 
> e.g:
> 
> Once:
> $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> $ cd linux-2.6
> 
> Then for each new tree you are interested in:
> linux-2.6$ git remote add ianc git://xenbits.xen.org/people/ianc/linux-2.6.git
> linux-2.6$ git fetch ianc
> [...pulls in updates from ianc...]
> linux-2.6$ git log ianc/irq-fairness
> 
> etc. See "git remote --help" for more info.
> 
> Since my irq-fairness branch likely doesn't stand alone you will
> probably need to merge it into your current 2.6.38 based head (something
> like Konrad's 2.6.38 branch for example). e.g.
> 
> linux-2.6$ git merge ianc/irq-fairness
> 
> Alternatively (and better) you can pull a single remote branch and merge
> it into your current head. e.g.
> linux-2.6$ git pull git://xenbits.xen.org/people/ianc/linux-2.6.git irq-fairness
> 
> Compared with the git merge approach this creates a more informative
> automated merge commit log.
> 
> The arguments to git pull are taken literally from the pull request:
> > > > The following changes since commit c5ae07bb307b658c8458f29ca77d237aec0f9327:
> > > > Ian Campbell (1):
> > > > xen: events: remove dom0 specific xen_create_msi_irq
> > > > 
> > > > are available in the git repository at:
> > > > 
> > > > git://xenbits.xen.org/people/ianc/linux-2.6.git irq-fairness
> 
> Ian.
> 
> 
 		 	   		  

[-- Attachment #1.2: Type: text/html, Size: 2990 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

RE: [GIT/PATCH 0/5] Re: unfair servicing of DomU vbd requests

[Ian Campbell]

On Fri, 2011-03-04 at 09:59 +0000, MaoXiaoyun wrote:
> 
> Thanks Ian.
>  
> I've just pull the code.
> But could the kernel be used as dom0, since I can't find blkback in
> driver/xen which is needed, right?
 
> And what is the usage of this branch?

It is a topic branch intended for a maintainer to pull into their tree.
It is not a standalone tree which you can just use -- that is why I
described below how to pull it into an existing base.

You will find that the majority of git branches are topic branches which
do not standalone. If you intend to be pulling peoples development
branches then I strongly recommend you google up some git documentation
and learn all about branches and merging etc.

Ian. 

>  
>  
> > Subject: RE: [GIT/PATCH 0/5] Re: [Xen-devel] unfair servicing of
> DomU vbd requests
> > From: Ian.Campbell@eu.citrix.com
> > To: tinnycloud@hotmail.com
> > CC: xen-devel@lists.xensource.com; james.harper@bendigoit.com.au
> > Date: Fri, 4 Mar 2011 07:21:29 +0000
> > 
> > On Fri, 2011-03-04 at 07:12 +0000, MaoXiaoyun wrote:
> > > I've tried to clone, but confront this error, did I do right?
> > 
> > Your command will try and clone my default branch, which I'm not
> sure I
> > have configured (I don't really want one since no branch is
> particularly
> > special in my tree).
> > 
> > I would recommend that instead of completely cloning a fresh tree
> for
> > each tree you are interested in that you just add a new remote to
> your
> > existing tree, which could be a clone of e..g xen.git or Linus'
> tree.
> > 
> > e.g:
> > 
> > Once:
> > $ git clone
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> > $ cd linux-2.6
> > 
> > Then for each new tree you are interested in:
> > linux-2.6$ git remote add ianc
> git://xenbits.xen.org/people/ianc/linux-2.6.git
> > linux-2.6$ git fetch ianc
> > [...pulls in updates from ianc...]
> > linux-2.6$ git log ianc/irq-fairness
> > 
> > etc. See "git remote --help" for more info.
> > 
> > Since my irq-fairness branch likely doesn't stand alone you will
> > probably need to merge it into your current 2.6.38 based head
> (something
> > like Konrad's 2.6.38 branch for example). e.g.
> > 
> > linux-2.6$ git merge ianc/irq-fairness
> > 
> > Alternatively (and better) you can pull a single remote branch and
> merge
> > it into your current head. e.g.
> > linux-2.6$ git pull git://xenbits.xen.org/people/ianc/linux-2.6.git
> irq-fairness
> > 
> > Compared with the git merge approach this creates a more informative
> > automated merge commit log.
> > 
> > The arguments to git pull are taken literally from the pull request:
> > > > > The following changes since commit
> c5ae07bb307b658c8458f29ca77d237aec0f9327:
> > > > > Ian Campbell (1):
> > > > > xen: events: remove dom0 specific xen_create_msi_irq
> > > > > 
> > > > > are available in the git repository at:
> > > > > 
> > > > > git://xenbits.xen.org/people/ianc/linux-2.6.git irq-fairness
> > 
> > Ian.
> > 
> > 

RE: [GIT/PATCH 0/5] Re: unfair servicing of DomU vbd requests

[MaoXiaoyun]

[-- Attachment #1.1: Type: text/plain, Size: 4314 bytes --]


Hi Ian:
 
   Sorry to bother again. 
   I've learnt git a bit, but still quite confused.
   I've done the operation below, which in my understanding, I've merged
irq-fairness branch into master. But the code is not complete, I need merge
more, as your said, such as Konrad's 2.6.38 branch. Well, I have no idea what kinds
of branch I need, and how to find them, do the branches exist in "git branch -r" or 
some place else?
 
 
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
$ cd linux-2.6
linux-2.6$ git remote add ianc git://xenbits.xen.org/people/ianc/linux-2.6.git
linux-2.6$ git fetch ianc

linux-2.6$ git merge ianc/irq-fairness
 
Git is not easy to learn, espescially on understaning kernel source management.
many thanks.

 
> Subject: RE: [GIT/PATCH 0/5] Re: [Xen-devel] unfair servicing of DomU vbd requests
> From: Ian.Campbell@eu.citrix.com
> To: tinnycloud@hotmail.com
> CC: xen-devel@lists.xensource.com; james.harper@bendigoit.com.au
> Date: Fri, 4 Mar 2011 10:06:03 +0000
> 
> On Fri, 2011-03-04 at 09:59 +0000, MaoXiaoyun wrote:
> > 
> > Thanks Ian.
> > 
> > I've just pull the code.
> > But could the kernel be used as dom0, since I can't find blkback in
> > driver/xen which is needed, right?
> 
> > And what is the usage of this branch?
> 
> It is a topic branch intended for a maintainer to pull into their tree.
> It is not a standalone tree which you can just use -- that is why I
> described below how to pull it into an existing base.
> 
> You will find that the majority of git branches are topic branches which
> do not standalone. If you intend to be pulling peoples development
> branches then I strongly recommend you google up some git documentation
> and learn all about branches and merging etc.
> 
> Ian. 
> 
> > 
> > 
> > > Subject: RE: [GIT/PATCH 0/5] Re: [Xen-devel] unfair servicing of
> > DomU vbd requests
> > > From: Ian.Campbell@eu.citrix.com
> > > To: tinnycloud@hotmail.com
> > > CC: xen-devel@lists.xensource.com; james.harper@bendigoit.com.au
> > > Date: Fri, 4 Mar 2011 07:21:29 +0000
> > > 
> > > On Fri, 2011-03-04 at 07:12 +0000, MaoXiaoyun wrote:
> > > > I've tried to clone, but confront this error, did I do right?
> > > 
> > > Your command will try and clone my default branch, which I'm not
> > sure I
> > > have configured (I don't really want one since no branch is
> > particularly
> > > special in my tree).
> > > 
> > > I would recommend that instead of completely cloning a fresh tree
> > for
> > > each tree you are interested in that you just add a new remote to
> > your
> > > existing tree, which could be a clone of e..g xen.git or Linus'
> > tree.
> > > 
> > > e.g:
> > > 
> > > Once:
> > > $ git clone
> > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> > > $ cd linux-2.6
> > > 
> > > Then for each new tree you are interested in:
> > > linux-2.6$ git remote add ianc
> > git://xenbits.xen.org/people/ianc/linux-2.6.git
> > > linux-2.6$ git fetch ianc
> > > [...pulls in updates from ianc...]
> > > linux-2.6$ git log ianc/irq-fairness
> > > 
> > > etc. See "git remote --help" for more info.
> > > 
> > > Since my irq-fairness branch likely doesn't stand alone you will
> > > probably need to merge it into your current 2.6.38 based head
> > (something
> > > like Konrad's 2.6.38 branch for example). e.g.
> > > 
> > > linux-2.6$ git merge ianc/irq-fairness
> > > 
> > > Alternatively (and better) you can pull a single remote branch and
> > merge
> > > it into your current head. e.g.
> > > linux-2.6$ git pull git://xenbits.xen.org/people/ianc/linux-2.6.git
> > irq-fairness
> > > 
> > > Compared with the git merge approach this creates a more informative
> > > automated merge commit log.
> > > 
> > > The arguments to git pull are taken literally from the pull request:
> > > > > > The following changes since commit
> > c5ae07bb307b658c8458f29ca77d237aec0f9327:
> > > > > > Ian Campbell (1):
> > > > > > xen: events: remove dom0 specific xen_create_msi_irq
> > > > > > 
> > > > > > are available in the git repository at:
> > > > > > 
> > > > > > git://xenbits.xen.org/people/ianc/linux-2.6.git irq-fairness
> > > 
> > > Ian.
> > > 
> > > 
> 
> 
 		 	   		  

[-- Attachment #1.2: Type: text/html, Size: 9897 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

RE: [GIT/PATCH 0/5] Re: unfair servicing of DomU vbd requests

[Ian Campbell]

On Mon, 2011-03-07 at 03:37 +0000, MaoXiaoyun wrote:
> Hi Ian:
>  
>    Sorry to bother again. 
>    I've learnt git a bit, but still quite confused.
>    I've done the operation below, which in my understanding, I've
> merged
> irq-fairness branch into master. But the code is not complete, I need
> merge
> more, as your said, such as Konrad's 2.6.38 branch. Well, I have no
> idea what kinds of branch I need, and how to find them, do the
> branches exist in "git branch -r" or some place else?

The point at which you did the merge below should have been with e.g.
Konrad's 2.6.38 branch as your current HEAD. In other words you need to
merge my irq-frairness branch _into_ an existing complete branch.

Ian.

>  
>  
> 
> 
> $ git clone
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> 
> $ cd linux-2.6
> 
> linux-2.6$ git remote add ianc
> git://xenbits.xen.org/people/ianc/linux-2.6.git
> 
> linux-2.6$ git fetch ianc
> 
> linux-2.6$ git merge ianc/irq-fairness
> 
>  
> Git is not easy to learn, espescially on understaning kernel source
> management.
> many thanks.
> 
>  
> > Subject: RE: [GIT/PATCH 0/5] Re: [Xen-devel] unfair servicing of
> DomU vbd requests
> > From: Ian.Campbell@eu.citrix.com
> > To: tinnycloud@hotmail.com
> > CC: xen-devel@lists.xensource.com; james.harper@bendigoit.com.au
> > Date: Fri, 4 Mar 2011 10:06:03 +0000
> > 
> > On Fri, 2011-03-04 at 09:59 +0000, MaoXiaoyun wrote:
> > > 
> > > Thanks Ian.
> > > 
> > > I've just pull the code.
> > > But could the kernel be used as dom0, since I can't find blkback
> in
> > > driver/xen which is needed, right?
> > 
> > > And what is the usage of this branch?
> > 
> > It is a topic branch intended for a maintainer to pull into their
> tree.
> > It is not a standalone tree which you can just use -- that is why I
> > described below how to pull it into an existing base.
> > 
> > You will find that the majority of git branches are topic branches
> which
> > do not standalone. If you intend to be pulling peoples development
> > branches then I strongly recommend you google up some git
> documentation
> > and learn all about branches and merging etc.
> > 
> > Ian. 
> > 
> > > 
> > > 
> > > > Subject: RE: [GIT/PATCH 0/5] Re: [Xen-devel] unfair servicing of
> > > DomU vbd requests
> > > > From: Ian.Campbell@eu.citrix.com
> > > > To: tinnycloud@hotmail.com
> > > > CC: xen-devel@lists.xensource.com; james.harper@bendigoit.com.au
> > > > Date: Fri, 4 Mar 2011 07:21:29 +0000
> > > > 
> > > > On Fri, 2011-03-04 at 07:12 +0000, MaoXiaoyun wrote:
> > > > > I've tried to clone, but confront this error, did I do right?
> > > > 
> > > > Your command will try and clone my default branch, which I'm not
> > > sure I
> > > > have configured (I don't really want one since no branch is
> > > particularly
> > > > special in my tree).
> > > > 
> > > > I would recommend that instead of completely cloning a fresh
> tree
> > > for
> > > > each tree you are interested in that you just add a new remote
> to
> > > your
> > > > existing tree, which could be a clone of e..g xen.git or Linus'
> > > tree.
> > > > 
> > > > e.g:
> > > > 
> > > > Once:
> > > > $ git clone
> > >
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> > > > $ cd linux-2.6
> > > > 
> > > > Then for each new tree you are interested in:
> > > > linux-2.6$ git remote add ianc
> > > git://xenbits.xen.org/people/ianc/linux-2.6.git
> > > > linux-2.6$ git fetch ianc
> > > > [...pulls in updates from ianc...]
> > > > linux-2.6$ git log ianc/irq-fairness
> > > > 
> > > > etc. See "git remote --help" for more info.
> > > > 
> > > > Since my irq-fairness branch likely doesn't stand alone you will
> > > > probably need to merge it into your current 2.6.38 based head
> > > (something
> > > > like Konrad's 2.6.38 branch for example). e.g.
> > > > 
> > > > linux-2.6$ git merge ianc/irq-fairness
> > > > 
> > > > Alternatively (and better) you can pull a single remote branch
> and
> > > merge
> > > > it into your current head. e.g.
> > > > linux-2.6$ git pull
> git://xenbits.xen.org/people/ianc/linux-2.6.git
> > > irq-fairness
> > > > 
> > > > Compared with the git merge approach this creates a more
> informative
> > > > automated merge commit log.
> > > > 
> > > > The arguments to git pull are taken literally from the pull
> request:
> > > > > > > The following changes since commit
> > > c5ae07bb307b658c8458f29ca77d237aec0f9327:
> > > > > > > Ian Campbell (1):
> > > > > > > xen: events: remove dom0 specific xen_create_msi_irq
> > > > > > > 
> > > > > > > are available in the git repository at:
> > > > > > > 
> > > > > > > git://xenbits.xen.org/people/ianc/linux-2.6.git
> irq-fairness
> > > > 
> > > > Ian.
> > > > 
> > > > 
> > 
> > 

RE: [GIT/PATCH 0/5] Re: unfair servicing of DomU vbd requests

[MaoXiaoyun]

[-- Attachment #1.1: Type: text/plain, Size: 5985 bytes --]


Ye, I understand more now.
 
I did follow:
 
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
$ cd linux-2.6
linux-2.6$ git remote add ianc git://xenbits.xen.org/people/ianc/linux-2.6.git
linux-2.6$ git fetch ianc

linux-2.6$ git merge ianc/irq-fairness

 
linux-2.6$ git remote add konrad git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
linux-2.6$ git fetch konrad

linux-2.6$ git merge konrad/devel/next-2.6.38
 
Hope I did it right.
Thanks.
 
> Subject: RE: [GIT/PATCH 0/5] Re: [Xen-devel] unfair servicing of DomU vbd requests
> From: Ian.Campbell@eu.citrix.com
> To: tinnycloud@hotmail.com
> CC: xen-devel@lists.xensource.com; james.harper@bendigoit.com.au
> Date: Mon, 7 Mar 2011 08:09:49 +0000
> 
> On Mon, 2011-03-07 at 03:37 +0000, MaoXiaoyun wrote:
> > Hi Ian:
> > 
> > Sorry to bother again. 
> > I've learnt git a bit, but still quite confused.
> > I've done the operation below, which in my understanding, I've
> > merged
> > irq-fairness branch into master. But the code is not complete, I need
> > merge
> > more, as your said, such as Konrad's 2.6.38 branch. Well, I have no
> > idea what kinds of branch I need, and how to find them, do the
> > branches exist in "git branch -r" or some place else?
> 
> The point at which you did the merge below should have been with e.g.
> Konrad's 2.6.38 branch as your current HEAD. In other words you need to
> merge my irq-frairness branch _into_ an existing complete branch.
> 
> Ian.
> 
> > 
> > 
> > 
> > 
> > $ git clone
> > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> > 
> > $ cd linux-2.6
> > 
> > linux-2.6$ git remote add ianc
> > git://xenbits.xen.org/people/ianc/linux-2.6.git
> > 
> > linux-2.6$ git fetch ianc
> > 
> > linux-2.6$ git merge ianc/irq-fairness
> > 
> > 
> > Git is not easy to learn, espescially on understaning kernel source
> > management.
> > many thanks.
> > 
> > 
> > > Subject: RE: [GIT/PATCH 0/5] Re: [Xen-devel] unfair servicing of
> > DomU vbd requests
> > > From: Ian.Campbell@eu.citrix.com
> > > To: tinnycloud@hotmail.com
> > > CC: xen-devel@lists.xensource.com; james.harper@bendigoit.com.au
> > > Date: Fri, 4 Mar 2011 10:06:03 +0000
> > > 
> > > On Fri, 2011-03-04 at 09:59 +0000, MaoXiaoyun wrote:
> > > > 
> > > > Thanks Ian.
> > > > 
> > > > I've just pull the code.
> > > > But could the kernel be used as dom0, since I can't find blkback
> > in
> > > > driver/xen which is needed, right?
> > > 
> > > > And what is the usage of this branch?
> > > 
> > > It is a topic branch intended for a maintainer to pull into their
> > tree.
> > > It is not a standalone tree which you can just use -- that is why I
> > > described below how to pull it into an existing base.
> > > 
> > > You will find that the majority of git branches are topic branches
> > which
> > > do not standalone. If you intend to be pulling peoples development
> > > branches then I strongly recommend you google up some git
> > documentation
> > > and learn all about branches and merging etc.
> > > 
> > > Ian. 
> > > 
> > > > 
> > > > 
> > > > > Subject: RE: [GIT/PATCH 0/5] Re: [Xen-devel] unfair servicing of
> > > > DomU vbd requests
> > > > > From: Ian.Campbell@eu.citrix.com
> > > > > To: tinnycloud@hotmail.com
> > > > > CC: xen-devel@lists.xensource.com; james.harper@bendigoit.com.au
> > > > > Date: Fri, 4 Mar 2011 07:21:29 +0000
> > > > > 
> > > > > On Fri, 2011-03-04 at 07:12 +0000, MaoXiaoyun wrote:
> > > > > > I've tried to clone, but confront this error, did I do right?
> > > > > 
> > > > > Your command will try and clone my default branch, which I'm not
> > > > sure I
> > > > > have configured (I don't really want one since no branch is
> > > > particularly
> > > > > special in my tree).
> > > > > 
> > > > > I would recommend that instead of completely cloning a fresh
> > tree
> > > > for
> > > > > each tree you are interested in that you just add a new remote
> > to
> > > > your
> > > > > existing tree, which could be a clone of e..g xen.git or Linus'
> > > > tree.
> > > > > 
> > > > > e.g:
> > > > > 
> > > > > Once:
> > > > > $ git clone
> > > >
> > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> > > > > $ cd linux-2.6
> > > > > 
> > > > > Then for each new tree you are interested in:
> > > > > linux-2.6$ git remote add ianc
> > > > git://xenbits.xen.org/people/ianc/linux-2.6.git
> > > > > linux-2.6$ git fetch ianc
> > > > > [...pulls in updates from ianc...]
> > > > > linux-2.6$ git log ianc/irq-fairness
> > > > > 
> > > > > etc. See "git remote --help" for more info.
> > > > > 
> > > > > Since my irq-fairness branch likely doesn't stand alone you will
> > > > > probably need to merge it into your current 2.6.38 based head
> > > > (something
> > > > > like Konrad's 2.6.38 branch for example). e.g.
> > > > > 
> > > > > linux-2.6$ git merge ianc/irq-fairness
> > > > > 
> > > > > Alternatively (and better) you can pull a single remote branch
> > and
> > > > merge
> > > > > it into your current head. e.g.
> > > > > linux-2.6$ git pull
> > git://xenbits.xen.org/people/ianc/linux-2.6.git
> > > > irq-fairness
> > > > > 
> > > > > Compared with the git merge approach this creates a more
> > informative
> > > > > automated merge commit log.
> > > > > 
> > > > > The arguments to git pull are taken literally from the pull
> > request:
> > > > > > > > The following changes since commit
> > > > c5ae07bb307b658c8458f29ca77d237aec0f9327:
> > > > > > > > Ian Campbell (1):
> > > > > > > > xen: events: remove dom0 specific xen_create_msi_irq
> > > > > > > > 
> > > > > > > > are available in the git repository at:
> > > > > > > > 
> > > > > > > > git://xenbits.xen.org/people/ianc/linux-2.6.git
> > irq-fairness
> > > > > 
> > > > > Ian.
> > > > > 
> > > > > 
> > > 
> > > 
> 
> 
 		 	   		  

[-- Attachment #1.2: Type: text/html, Size: 11416 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

RE: [GIT/PATCH 0/5] Re: unfair servicing of DomU vbd requests

[MaoXiaoyun]

[-- Attachment #1.1: Type: text/plain, Size: 3057 bytes --]


Hi James.
 
I go through the patch, since all its changes happens inside __xen_evtchn_do_upcall(),
so I apply the patch into my 2.6.31.kernel by manual. (I was failed to merge a usable, 
2.6.38dom0, since quite a lot branch needed, such as blkback, netback)
 
But still, the blue screen shows up. Log attached.
Is the timeout better than before?
 
Beside, I think I need find some to examine my harddisk.  

 
> Subject: FW: [GIT/PATCH 0/5] Re: [Xen-devel] unfair servicing of DomU vbd requests
> Date: Fri, 4 Mar 2011 09:26:44 +1100
> From: james.harper@bendigoit.com.au
> To: tinnycloud@hotmail.com
> 
> Ian has posted some patches to xen-devel. Can you apply them to your Dom0 kernel and see if they fix your i/o servicing problem?
> 
> As I understand it, without this patch Dom0 will service the lowest event channel first, so if there is always an io request on the lower channel the higher channels will never get serviced. A bad disk would aggravate this situation but isn't really the cause of it.
> 
> James
> 
> > -----Original Message-----
> > From: Ian Campbell [mailto:Ian.Campbell@citrix.com]
> > Sent: Friday, 4 March 2011 04:10
> > To: Keir Fraser
> > Cc: James Harper; xen devel; Konrad Rzeszutek Wilk; Jeremy Fitzhardinge
> > Subject: [GIT/PATCH 0/5] Re: [Xen-devel] unfair servicing of DomU vbd requests
> > 
> > On Thu, 2011-03-03 at 08:30 +0000, Keir Fraser wrote:
> > > Without the round-robin servicing, unfairness to the point of starvation is
> > > a distinct possibility.
> > 
> > Indeed. The following is a forward port of these patches from
> > 2.6.18-xen.hg:
> > * 324:7fe1c6d02a2b
> > * 325:b2768401db94
> > * 988:c88a02a22a05
> > * 990:427276ac595d
> > * 991:9ba6d9f3fbc0
> > 
> > Hopefully I didn't miss any.
> > 
> > The switch in pvops from "l1"/"l2" naming convention to "word"/"bit"
> > made the conflict resolution a bit prone to thinkos but hopefully I
> > didn't b0rk it too badly. Review with that in mind greatly appreciated.
> > 
> > boots a dom0 + a pv guest.
> > 
> > Pull request on top of konrad/stable/irq.cleanup:
> > 
> > The following changes since commit c5ae07bb307b658c8458f29ca77d237aec0f9327:
> > Ian Campbell (1):
> > xen: events: remove dom0 specific xen_create_msi_irq
> > 
> > are available in the git repository at:
> > 
> > git://xenbits.xen.org/people/ianc/linux-2.6.git irq-fairness
> > 
> > Ian Campbell (1):
> > xen: events: Make last processed event channel a per-cpu variable.
> > 
> > Keir Fraser (3):
> > xen: events: Clean up round-robin evtchn scan.
> > xen: events: Make round-robin scan fairer by snapshotting each l2 word
> > xen: events: Remove redundant clear of l2i at end of round-robin loop
> > 
> > Scott Rixner (1):
> > xen: events: Process event channels notifications in round-robin order.
> > 
> > drivers/xen/events.c | 80 +++++++++++++++++++++++++++++++++++++++++++++----
> > -
> > 1 files changed, 72 insertions(+), 8 deletions(-)
> > 
> > 
> > 
> > Ian.
> > 
> > 
> > 
> 
 		 	   		  

[-- Attachment #1.2: Type: text/html, Size: 3881 bytes --]

[-- Attachment #2: qemu-dm-w3.MR_cp7.vhd.log --]
[-- Type: text/plain, Size: 41746 bytes --]

domid: 7
Watching /local/domain/0/device-model/7/logdirty/cmd
Watching /local/domain/0/device-model/7/command
char device redirected to /dev/pts/15
qemu_map_cache_init nr_buckets = 10000 size 4194304
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = 9f756e9c-42a4-7d83-6536-97d541de577b
Time offset set 0
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
xs_read(/local/domain/0/device-model/7/xen_extended_power_mgmt): read error
xs_read(): vncpasswd get error. /vm/9f756e9c-42a4-7d83-6536-97d541de577b/vncpasswd.
Log-dirty: no command yet.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
xs_read(/local/domain/7/log-throttling): read error
qemu: ignoring not-understood drive `/local/domain/7/log-throttling'
medium change watch on `/local/domain/7/log-throttling' - unknown device, ignored
cirrus vga map change while on lfb mode
mapping vram to f0000000 - f0400000
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state.
12943981237375: XenPCI <-- XenPci_HighSyncCallFunctionN
12943981237375: XenPCI <-- XenPci_HighSyncCallFunction0
12943981237375: XenPCI     Waiting for highsync_complete_event
12943981237375: XenPCI <-- XenPci_HighSync
12943981237375: XenPCI --> XenPci_InitialBalloonDown
12943981237390: XenPCI     base = 0x40000000, Xen Signature = XenVMMXenVMM, EAX = 0x40000003
12943981237390: XenPCI     Hypercall area at 89DB5000
12943981237390: XenPCI     XENMEM_maximum_reservation = 525312
12943981237390: XenPCI     XENMEM_current_reservation = 131288
12943981237390: XenPCI     Trying to give 1540 MB to Xen
12943981245609: XenPCI <-- XenPci_InitialBalloonDown
12943981245609: XenPCI     KeInitializeCrashDumpHeader status = 00000000, size = 4096
12943981245625: XenPCI GPLPV 0.10.0.3
12943981245625: XenPCI --> XenPci_FixLoadOrder
12943981245625: XenPCI     dummy_group_index = 1
12943981245890: XenPCI     wdf_load_group_index = 2
12943981245968: XenPCI     xenpci_group_index = 3
12943981245968: XenPCI     boot_bus_extender_index = 4
12943981246046: XenPCI <-- XenPci_FixLoadOrder
12943981246062: XenPCI     Version = 1
Unknown PV product 2 loaded in guest
PV driver build 1
12943981246578: XenPCI     Disabled qemu devices 03
12943981246593: XenPCI <-- DriverEntry
12943981248203: XenPCI     Xen PCI device found - must be fdo
12943981248203: XenPCI --> XenPci_EvtDeviceAdd_XenPci
12943981248203: XenPCI <-- XenPci_EvtDeviceAdd_XenPci
12943981248234: XenPCI --> XenPci_EvtDevicePrepareHardware
12943981248234: XenPCI     IoPort Address(c000) Length: 256
12943981248234: XenPCI     Private Data: 0x01 0x00 0x00
12943981248234: XenPCI     Memory mapped CSR:(f2000000:0) Length:(16777216)
12943981248234: XenPCI     Memory flags = 0004
12943981248281: XenPCI     Private Data: 0x01 0x01 0x00
12943981248296: XenPCI     irq_number = 01c
12943981248296: XenPCI     irq_vector = 1a3
12943981248296: XenPCI     irq_level = 009
12943981248296: XenPCI     irq_mode = LevelSensitive
12943981248312: XenPCI     ShareDisposition = CmResourceShareShared
12943981248312: XenPCI <-- XenPci_EvtDevicePrepareHardware
12943981248312: XenPCI --> XenPci_EvtDeviceD0Entry
12943981248312: XenPCI     WdfPowerDeviceD3Final
12943981248328: XenPCI --> XenPci_Init
12943981248328: XenPCI     base = 0x40000000, Xen Signature = XenVMMXenVMM, EAX = 0x40000003
12943981248328: XenPCI     Hypercall area at 89B62000
12943981248343: XenPCI     shared_info_area_unmapped.QuadPart = f2000000
12943981248343: XenPCI     gpfn = f2000
12943981248343: XenPCI     hypervisor memory op (XENMAPSPACE_shared_info) ret = 0
12943981248359: XenPCI <-- XenPci_Init
12943981248359: XenPCI --> GntTbl_Init
12943981248359: XenPCI     grant_frames = 32
12943981248359: XenPCI     grant_entries = 16384
12943981248359: XenPCI     pfn = 98ad
12943981248359: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98ad
12943981248375: XenPCI     decreased 1 pages for grant table frame 0
12943981248375: XenPCI     pfn = 98ae
12943981248390: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98ae
12943981248390: XenPCI     decreased 1 pages for grant table frame 1
12943981248390: XenPCI     pfn = 98af
12943981248390: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98af
12943981248406: XenPCI     decreased 1 pages for grant table frame 2
12943981248406: XenPCI     pfn = 98b0
12943981248406: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98b0
12943981248437: XenPCI     decreased 1 pages for grant table frame 3
12943981248453: XenPCI     pfn = 98b1
12943981248468: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98b1
12943981248484: XenPCI     decreased 1 pages for grant table frame 4
12943981248484: XenPCI     pfn = 98b2
12943981248484: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98b2
12943981248500: XenPCI     decreased 1 pages for grant table frame 5
12943981248500: XenPCI     pfn = 98b3
12943981248500: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98b3
12943981248500: XenPCI     decreased 1 pages for grant table frame 6
12943981248500: XenPCI     pfn = 98b4
12943981248500: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98b4
12943981248515: XenPCI     decreased 1 pages for grant table frame 7
12943981248515: XenPCI     pfn = 98b5
12943981248515: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98b5
12943981248515: XenPCI     decreased 1 pages for grant table frame 8
12943981248515: XenPCI     pfn = 98b6
12943981248515: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98b6
12943981248531: XenPCI     decreased 1 pages for grant table frame 9
12943981248531: XenPCI     pfn = 98b7
12943981248531: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98b7
12943981248531: XenPCI     decreased 1 pages for grant table frame 10
12943981248531: XenPCI     pfn = 98b8
12943981248531: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98b8
12943981248546: XenPCI     decreased 1 pages for grant table frame 11
12943981248546: XenPCI     pfn = 98b9
12943981248546: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98b9
12943981248546: XenPCI     decreased 1 pages for grant table frame 12
12943981248546: XenPCI     pfn = 98ba
12943981248546: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98ba
12943981248546: XenPCI     decreased 1 pages for grant table frame 13
12943981248546: XenPCI     pfn = 98bb
12943981248562: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98bb
12943981248562: XenPCI     decreased 1 pages for grant table frame 14
12943981248578: XenPCI     pfn = 98bc
12943981248578: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98bc
12943981248578: XenPCI     decreased 1 pages for grant table frame 15
12943981248593: XenPCI     pfn = 98bd
12943981249031: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98bd
12943981249125: XenPCI     decreased 1 pages for grant table frame 16
12943981249140: XenPCI     pfn = 98be
12943981249375: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98be
12943981249531: XenPCI     decreased 1 pages for grant table frame 17
12943981249625: XenPCI     pfn = 98bf
12943981249625: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98bf
12943981249625: XenPCI     decreased 1 pages for grant table frame 18
12943981249625: XenPCI     pfn = 98c0
12943981249625: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98c0
12943981249765: XenPCI     decreased 1 pages for grant table frame 19
12943981250156: XenPCI     pfn = 98c1
12943981250156: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98c1
12943981250281: XenPCI     decreased 1 pages for grant table frame 20
12943981250281: XenPCI     pfn = 98c2
12943981250281: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98c2
12943981250375: XenPCI     decreased 1 pages for grant table frame 21
12943981250375: XenPCI     pfn = 98c3
12943981250453: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98c3
12943981250468: XenPCI     decreased 1 pages for grant table frame 22
12943981250468: XenPCI     pfn = 98c4
12943981250468: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98c4
12943981250484: XenPCI     decreased 1 pages for grant table frame 23
12943981250734: XenPCI     pfn = 98c5
12943981250734: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98c5
12943981250734: XenPCI     decreased 1 pages for grant table frame 24
12943981250750: XenPCI     pfn = 98c6
12943981250859: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98c6
12943981250875: XenPCI     decreased 1 pages for grant table frame 25
12943981251156: XenPCI     pfn = 98c7
12943981251171: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98c7
12943981251171: XenPCI     decreased 1 pages for grant table frame 26
12943981251171: XenPCI     pfn = 98c8
12943981251171: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98c8
12943981251265: XenPCI     decreased 1 pages for grant table frame 27
12943981251343: XenPCI     pfn = 98c9
12943981251343: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98c9
12943981251343: XenPCI     decreased 1 pages for grant table frame 28
12943981251343: XenPCI     pfn = 98ca
12943981251343: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98ca
12943981251687: XenPCI     decreased 1 pages for grant table frame 29
12943981251703: XenPCI     pfn = 98cb
12943981251703: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98cb
12943981251765: XenPCI     decreased 1 pages for grant table frame 30
12943981251765: XenPCI     pfn = 98cc
12943981251812: XenPCI     Calling HYPERVISOR_memory_op - pfn = 98cc
12943981251812: XenPCI     decreased 1 pages for grant table frame 31
12943981251828: XenPCI --> GntTbl_Map
12943981252156: XenPCI <-- GntTbl_Map
12943981252156: XenPCI <-- GntTbl_Init
12943981252156: XenPCI --> EvtChn_Init
12943981252156: XenPCI --> _hvm_set_parameter
12943981252171: XenPCI HYPERVISOR_hvm_op retval = 0
12943981252296: XenPCI <-- _hvm_set_parameter
12943981252296: XenPCI     hvm_set_parameter(HVM_PARAM_CALLBACK_IRQ, 28) = 0
12943981252312: XenPCI --> EvtChn_AllocIpi
12943981252312: XenPCI <-- EvtChn_AllocIpi
12943981252312: XenPCI --> EvtChn_BindDpc
12943981252453: XenPCI <-- EvtChn_BindDpc
12943981252453: XenPCI     pdo_event_channel = 5
12943981252453: XenPCI <-- EvtChn_Init
12943981252453: XenPCI <-- XenPci_EvtDeviceD0Entry
12943981252781: XenPCI --> EvtChn_EvtInterruptEnable
12943981252796: XenPCI <-- EvtChn_EvtInterruptEnable
12943981252796: XenPCI --> XenPci_EvtDeviceD0EntryPostInterruptsEnabled
12943981252796: XenPCI --> XenBus_Init
12943981252796: XenPCI --> _hvm_get_parameter
12943981252812: XenPCI HYPERVISOR_hvm_op retval = 0
12943981252812: XenPCI <-- _hvm_get_parameter
12943981252812: XenPCI --> _hvm_get_parameter
12943981252812: XenPCI HYPERVISOR_hvm_op retval = 0
12943981252812: XenPCI <-- _hvm_get_parameter
12943981252828: XenPCI --> EvtChn_BindDpc
12943981252828: XenPCI <-- EvtChn_BindDpc
12943981252828: XenPCI <-- XenBus_Init
12943981252843: XenPCI     suspend event channel = 6
12943981252843: XenPCI --> EvtChn_BindDpc
12943981252843: XenPCI <-- EvtChn_BindDpc
12943981252859: XenPCI --> XenPci_SysrqHandler
12943981252859: XenPCI     SysRq Value = (null)
12943981252859: XenPCI <-- XenPci_SysrqHandler
12943981252859: XenPCI --> XenPci_ShutdownHandler
12943981252953: XenPCI     Initial Memory Value = 512 (524288)
12943981252968: Error reading shutdown path - ENOENT
12943981252968: XenPCI --> XenPci_BalloonThreadProc
12943981252968: XenPCI <-- XenPci_ShutdownHandler
12943981252968: XenPCI     low_mem_event = 89D7E030, state = 0
12943981252984: XenPCI --> XenPci_DeviceWatchHandler
12943981252984: XenPCI <-- XenPci_DeviceWatchHandler
12943981252984: XenPCI <-- XenPci_EvtDeviceD0EntryPostInterruptsEnabled
12943981252984: XenPCI --> XenPci_BalloonHandler
12943981252984: XenPCI --> XenPci_EvtChildListScanForChildren
12943981253000: XenPCI     target memory value = 512 (524288)
12943981253000: XenPCI <-- XenPci_BalloonHandler
12943981253000: XenPCI     Got balloon event, current = 512, target = 512
12943981253015: XenPCI     No change to memory
12943981253015: XenPCI     Found path = device/vbd/768
12943981253031: XenPCI     Found path = device/vif/0
12943981253031: XenPCI <-- XenPci_EvtChildListScanForChildren
12943981253046: XenPCI --> XenPci_EvtChildListCreateDevice
12943981253062: XenPCI     device = 'vbd', index = '768', path = 'device/vbd/768'
12943981253078: XenPCI <-- XenPci_EvtChildListCreateDevice
12943981253078: XenPCI --> XenPci_EvtChildListCreateDevice
12943981253078: XenPCI     device = 'vif', index = '0', path = 'device/vif/0'
12943981253078: XenPCI <-- XenPci_EvtChildListCreateDevice
12943981255078: XenVbd --> DriverEntry
12943981255093: XenVbd     IRQL = 0
12943981255093: XenVbd     DriverObject = 89A9FE18, RegistryPath = 80090BF8
12943981255125: XenVbd <-- DriverEntry
12943981255140: XenPCI --> XenPciPdo_EvtDeviceWdmIrpPreprocess_START_DEVICE
12943981255140: XenPCI     device/vbd/768
12943981255156: XenPCI     CmResourceTypeMemory (0)
12943981255156: XenPCI     Start = f2000000, Length = 0
12943981255156: XenPCI     pfn[0] = 0001f3a2
12943981255156: XenPCI     New Start = 000000001f3a2000, Length = 4096
12943981255171: XenPCI     CmResourceTypeMemory (1)
12943981255171: XenPCI     Start = f2000001, Length = 0
12943981255296: XenPCI <-- XenPciPdo_EvtDeviceWdmIrpPreprocess_START_DEVICE
12943981255312: XenPCI --> XenPciPdo_EvtDevicePrepareHardware
12943981255359: XenPCI <-- XenPciPdo_EvtDevicePrepareHardware
12943981255359: XenPCI --> XenPciPdo_EvtDeviceD0Entry
12943981255390: XenPCI     path = device/vbd/768
12943981255515: XenPCI     WdfPowerDeviceD3Final
12943981255515: XenPCI --> XenPci_GetBackendAndAddWatch
12943981255890: XenPCI <-- XenPci_GetBackendAndAddWatch
12943981255890: XenPCI --> XenPci_UpdateBackendState
12943981255921: XenPCI --> XenConfig_InitConfigPage
12943981256000: XenPCI     fdo_driver_object = 89A9FE18
12943981256015: XenPCI     fdo_driver_extension = 89AD8008
12943981256015: XenPCI <-- XenConfig_InitConfigPage
12943981256015: XenPCI --> XenPci_XenConfigDeviceSpecifyBuffers
12943981256187: XenPCI     XEN_INIT_TYPE_RING - ring-ref = 89A9E000
12943981256187: XenPCI     XEN_INIT_TYPE_RING - ring-ref = 16383
12943981256187: XenPCI     Backend State Changed to InitWait
12943981256187: XenPCI     XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 7
12943981256187: XenPCI <-- XenPci_UpdateBackendState
12943981256359: XenPCI --> XenPci_DeviceWatchHandler
12943981256359: XenPCI <-- XenPci_DeviceWatchHandler
12943981256359: XenPCI --> XenPci_DeviceWatchHandler
12943981257171: XenPCI <-- XenPci_DeviceWatchHandler
12943981257468: XenPCI --> EvtChn_BindIrq
12943981257468: XenPCI <-- EvtChn_BindIrq
12943981257468: XenPCI --> XenPci_ChangeFrontendStateMap
12943981257468: XenPCI --> XenPci_ChangeFrontendState
12943981257515: XenPCI --> XenPci_DeviceWatchHandler
12943981257578: XenPCI <-- XenPci_DeviceWatchHandler
12943981257906: XenPCI --> XenPci_UpdateBackendState
12943981257937: XenPCI     Backend State Changed to Connected
12943981257937: XenPCI <-- XenPci_UpdateBackendState
12943981257937: XenPCI <-- XenPci_ChangeFrontendState
12943981257953: XenPCI <-- XenPci_ChangeFrontendStateMap
12943981257953: XenPCI --> XenPci_ChangeFrontendStateMap
12943981257953: XenPCI <-- XenPci_ChangeFrontendStateMap
12943981257953: XenPCI <-- XenPci_XenConfigDeviceSpecifyBuffers
12943981257968: XenPCI <-- XenPciPdo_EvtDeviceD0Entry
12943981257968: XenVbd --> XenVbd_HwScsiFindAdapter
12943981257968: XenVbd     IRQL = 0
12943981257968: XenVbd     xvdd = 89889004
12943981257984: XenVbd     BusInterruptLevel = 28
12943981257984: XenVbd     BusInterruptVector = 01c
12943981257984: XenVbd     NumberOfAccessRanges = 1
12943981257984: XenVbd     RangeStart = 1f3a2000, RangeLength = 00001000
12943981257984: XenVbd     XEN_INIT_TYPE_VECTORS
12943981258000: XenVbd     XEN_INIT_TYPE_DEVICE_STATE - 899B53CC
12943981258000: XenVbd     XEN_INIT_TYPE_RING - ring-ref = 89A9E000
12943981258000: XenVbd     XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 7
12943981258015: XenVbd     XEN_INIT_TYPE_READ_STRING - device-type = disk
12943981258015: XenVbd     device-type = Disk
12943981258015: XenVbd     XEN_INIT_TYPE_READ_STRING - mode = w
12943981258015: XenVbd     mode = w
12943981258015: XenVbd     XEN_INIT_TYPE_READ_STRING - sectors = 104857600
12943981258031: XenVbd     XEN_INIT_TYPE_READ_STRING - sector-size = 512
12943981258046: XenVbd     XEN_INIT_TYPE_GRANT_ENTRIES - entries = 11
12943981258062: XenVbd     qemu_hide_flags_value = 3
12943981258062: XenVbd     aligned_buffer_data = 8988B280
12943981258078: XenVbd     aligned_buffer = 8988C000
12943981258093: XenVbd     ConfigInfo->MaximumTransferLength = 45056
12943981258109: XenVbd     ConfigInfo->NumberOfPhysicalBreaks = 10
12943981258125: XenVbd     ConfigInfo->CachesData was initialised to 0
12943981258125: XenVbd     Dma64BitAddresses not supported
12943981258125: XenVbd <-- XenVbd_HwScsiFindAdapter
12943981258140: XenVbd --> XenVbd_HwScsiInitialize
12943981258140: XenVbd     IRQL = 9
12943981258156: XenVbd     dump_mode = 0
12943981258156: XenVbd <-- XenVbd_HwScsiInitialize
12943981258156: XenVbd --> XenVbd_HwScsiAdapterControl
12943981258156: XenVbd     IRQL = 0
12943981258156: XenVbd     xvdd = 89889004
12943981258171: XenVbd     ScsiQuerySupportedControlTypes (Max = 5)
12943981258171: XenVbd <-- XenVbd_HwScsiAdapterControl
12943981258171: XenVbd --- HwScsiStartIo (Still figuring out ring)
12943981258187: XenVbd     ring_detect_state = 1, index = 0, operation = ff, id = 0, status = 0
12943981258203: XenVbd     req_prod = 2, rsp_prod = 2, rsp_cons = 0
12943981258218: XenVbd     ring_detect_state = 2, index = 1, operation = 0, id = ff, status = 0
12943981258218: XenVbd     req_prod = 2, rsp_prod = 2, rsp_cons = 0
12943981258218: XenVbd     switching to 'other' ring size
12943981258593: XenVbd     SRB_FUNCTION_IO_CONTROL
12943981258593: XenVbd     SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 28, allocation_length = 192
12943981258593: XenVbd     EXECUTE_SCSI Command = 1A returned error 00
12943981258593: XenVbd     SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192
12943981258937: XenVbd     SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 12
12943981307937: XenNet --> DriverEntry
12943981307937: XenNet     DriverObject = 89A11D50, RegistryPath = 89A13000
12943981307937: XenNet     NdisGetVersion = 50001
12943981307937: XenNet     ndis_wrapper_handle = 00000000
12943981307953: XenNet     ndis_wrapper_handle = 89A987C8
12943981307953: XenNet     NdisMInitializeWrapper succeeded
12943981307953: XenNet     MajorNdisVersion = 5,  MinorNdisVersion = 1
12943981307968: XenNet     about to call NdisMRegisterMiniport
12943981307968: XenNet     called NdisMRegisterMiniport
12943981307968: XenNet <-- DriverEntry
12943981308500: XenPCI --> XenPciPdo_EvtDeviceWdmIrpPreprocess_START_DEVICE
12943981308500: XenPCI     device/vif/0
12943981308515: XenPCI     CmResourceTypeMemory (0)
12943981308515: XenPCI     Start = f2000000, Length = 0
12943981308515: XenPCI     pfn[0] = 0001f362
12943981308515: XenPCI     New Start = 000000001f362000, Length = 4096
12943981308515: XenPCI     CmResourceTypeMemory (1)
12943981308515: XenPCI     Start = f2000001, Length = 0
12943981308515: XenPCI <-- XenPciPdo_EvtDeviceWdmIrpPreprocess_START_DEVICE
12943981308531: XenPCI --> XenPciPdo_EvtDevicePrepareHardware
12943981308531: XenPCI <-- XenPciPdo_EvtDevicePrepareHardware
12943981308531: XenPCI --> XenPciPdo_EvtDeviceD0Entry
12943981308531: XenPCI     path = device/vif/0
12943981308546: XenPCI     WdfPowerDeviceD3Final
12943981308546: XenPCI --> XenPci_GetBackendAndAddWatch
12943981308546: XenPCI <-- XenPci_GetBackendAndAddWatch
12943981308546: XenPCI --> XenPci_UpdateBackendState
12943981308578: XenPCI --> XenConfig_InitConfigPage
12943981308625: XenPCI     fdo_driver_object = 89A11D50
12943981308656: XenPCI     fdo_driver_extension = 00000000
12943981308656: XenPCI     fdo_driver_object = 89D684A8
12943981308671: XenPCI     fdo_driver_extension = 00000000
12943981308671: XenPCI <-- XenConfig_InitConfigPage
12943981308687: XenPCI --> XenPci_XenConfigDeviceSpecifyBuffers
12943981308687: XenPCI --> XenPci_ChangeFrontendStateMap
12943981308703: XenPCI <-- XenPci_ChangeFrontendStateMap
12943981308703: XenPCI     Backend State Changed to InitWait
12943981308703: XenPCI --> XenPci_ChangeFrontendStateMap
12943981308703: XenPCI <-- XenPci_UpdateBackendState
12943981308703: XenPCI <-- XenPci_ChangeFrontendStateMap
12943981308718: XenPCI <-- XenPci_XenConfigDeviceSpecifyBuffers
12943981308718: XenPCI <-- XenPciPdo_EvtDeviceD0Entry
12943981308718: XenNet --> XenNet_Init
12943981308718: XenNet     IRQL = 0
12943981308718: XenNet     nrl_length = 40
12943981308718: XenNet     irq_vector = 01c, irq_level = 01c, irq_mode = NdisInterruptLevelSensitive
12943981308734: XenNet     XEN_INIT_TYPE_13
12943981308750: XenNet     XEN_INIT_TYPE_VECTORS
12943981308750: XenNet     XEN_INIT_TYPE_DEVICE_STATE - 89AA1FB4
12943981308750: ScatterGather = 1
12943981308765: LargeSendOffload = 61440
12943981308765: ChecksumOffload = 1
12943981308765: ChecksumOffloadRxCheck = 1
12943981308765: MTU = 1500
12943981308765: RxInterruptModeration = 0
12943981308765: Could not read NetworkAddress value (c0000001) or value is invalid
12943981308812: XenNet --> XenNet_D0Entry
12943981308812: XenPCI --> XenPci_XenConfigDeviceSpecifyBuffers
12943981308828: XenPCI     XEN_INIT_TYPE_RING - tx-ring-ref = 899EE000
12943981308828: XenPCI     XEN_INIT_TYPE_RING - tx-ring-ref = 16268
12943981308921: XenPCI --> XenPci_DeviceWatchHandler
12943981308921: XenPCI     XEN_INIT_TYPE_RING - rx-ring-ref = 897E7000
12943981308921: XenPCI <-- XenPci_DeviceWatchHandler
12943981308921: XenPCI     XEN_INIT_TYPE_RING - rx-ring-ref = 16114
12943981308953: XenPCI --> XenPci_DeviceWatchHandler
12943981308953: XenPCI     XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 8
12943981308953: XenPCI <-- XenPci_DeviceWatchHandler
12943981309218: XenPCI --> EvtChn_Bind
12943981309218: XenPCI --> XenPci_DeviceWatchHandler
12943981309218: XenPCI <-- EvtChn_Bind
12943981309218: XenPCI <-- XenPci_DeviceWatchHandler
12943981309546: XenPCI --> XenPci_DeviceWatchHandler
12943981309546: XenPCI <-- XenPci_DeviceWatchHandler
12943981309765: XenPCI --> XenPci_DeviceWatchHandler
12943981309765: XenPCI <-- XenPci_DeviceWatchHandler
12943981309765: XenPCI --> XenPci_DeviceWatchHandler
12943981309765: XenPCI <-- XenPci_DeviceWatchHandler
12943981309781: XenPCI --> XenPci_DeviceWatchHandler
12943981309781: XenPCI <-- XenPci_DeviceWatchHandler
12943981309781: XenPCI --> XenPci_DeviceWatchHandler
12943981309781: XenPCI --> XenPci_ChangeFrontendStateMap
12943981309812: XenPCI <-- XenPci_DeviceWatchHandler
12943981309812: XenPCI <-- XenPci_ChangeFrontendStateMap
12943981310078: XenPCI --> XenPci_ChangeFrontendStateMap
12943981310093: XenPCI --> XenPci_ChangeFrontendState
12943981310109: XenPCI --> XenPci_DeviceWatchHandler
12943981310109: XenPCI <-- XenPci_DeviceWatchHandler
12943981312531: XenPCI --> XenPci_UpdateBackendState
12943981312578: XenPCI     state unchanged
12943981312578: XenPCI     Still waiting for 4 (currently 2)...
12943981312812: XenPCI --> XenPci_UpdateBackendState
12943981312859: XenPCI     Backend State Changed to Connected
12943981313015: XenPCI <-- XenPci_ChangeFrontendState
12943981313015: XenPCI <-- XenPci_UpdateBackendState
12943981313171: XenPCI <-- XenPci_ChangeFrontendStateMap
12943981313187: XenPCI <-- XenPci_XenConfigDeviceSpecifyBuffers
12943981313187: XenNet --> XenNet_ConnectBackend
12943981313203: XenNet     XEN_INIT_TYPE_13
12943981313203: XenNet     XEN_INIT_TYPE_VECTORS
12943981313218: XenNet     XEN_INIT_TYPE_DEVICE_STATE - 89AA1FB4
12943981313218: XenNet     XEN_INIT_TYPE_RING - tx-ring-ref = 899EE000
12943981313218: XenNet     XEN_INIT_TYPE_RING - rx-ring-ref = 897E7000
12943981313375: XenNet     XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 8
12943981313375: XenNet     XEN_INIT_TYPE_READ_STRING - mac = 00:16:3e:76:4b:7e
12943981313578: XenNet     XEN_INIT_TYPE_READ_STRING - feature-sg = 1
12943981313578: XenNet     XEN_INIT_TYPE_READ_STRING - feature-gso-tcpv4 = 1
12943981313578: XenNet     XEN_INIT_TYPE_17
12943981313578: XenNet <-- XenNet_ConnectBackend
12943981313578: XenNet --> XenNet_RxInit
12943981313593: XenNet <-- XenNet_RxInit
12943981313609: XenNet <-- XenNet_D0Entry
12943981313765: Get Unknown OID 0x10202
12943981313765: XenNet --> XenNet_PnPEventNotify
12943981313765: XenNet     NdisDevicePnPEventPowerProfileChanged
12943981313765: XenNet <-- XenNet_PnPEventNotify
12943981316765: Get Unknown OID 0x10201
12943981317015: Get Unknown OID 0xfc010210
12943981317015: Get OID_TCP_TASK_OFFLOAD
12943981317015: XenNet     (BUFFER_TOO_SHORT 100 > 28)
12943981317031: Get OID_TCP_TASK_OFFLOAD
12943981317031: config_csum enabled
12943981317031: nto = 89456D9C
12943981317031: nto->Size = 24
12943981317031: nto->TaskBufferLength = 16
12943981317031: config_gso enabled
12943981317109: nto = 89456DC0
12943981317125: nto->Size = 24
12943981317156: nto->TaskBufferLength = 16
12943981317156: &(nttls->IpOptions) = 89456DE1
12943981317156: Set OID_TCP_TASK_OFFLOAD
12943981317171: TcpIpChecksumNdisTask
12943981317171:   V4Transmit.IpOptionsSupported  = 0
12943981317171:   V4Transmit.TcpOptionsSupported = 1
12943981317171:   V4Transmit.TcpChecksum         = 1
12943981317203:   V4Transmit.UdpChecksum         = 0
12943981317203:   V4Transmit.IpChecksum          = 0
12943981317218:   V4Receive.IpOptionsSupported   = 0
12943981317218:   V4Receive.TcpOptionsSupported  = 0
12943981317250:   V4Receive.TcpChecksum          = 1
12943981317250:   V4Receive.UdpChecksum          = 0
12943981317265:   V4Receive.IpChecksum           = 0
12943981317265:   V6Transmit.IpOptionsSupported  = 0
12943981317281:   V6Transmit.TcpOptionsSupported = 0
12943981317296:   V6Transmit.TcpChecksum         = 0
12943981317328:   V6Transmit.UdpChecksum         = 0
12943981317328:   V6Receive.IpOptionsSupported   = 0
12943981317343:   V6Receive.TcpOptionsSupported  = 0
12943981317343:   V6Receive.TcpChecksum          = 0
12943981317359:   V6Receive.UdpChecksum          = 0
12943981317375: TcpLargeSendNdisTask
12943981317390:   MaxOffLoadSize                 = 61440
12943981317421:   MinSegmentCount                = 4
12943981317421:   TcpOptions                     = 0
12943981317437:   IpOptions                      = 0
12943981317453: Get OID_PNP_CAPABILITIES
12943981317453: Set Unknown OID 0x10119
12943981317453: Set OID_GEN_CURRENT_LOOKAHEAD 128 (897E8000)
12943981317546: Set OID_GEN_CURRENT_PACKET_FILTER (xi = 897E8000)
12943981317546:   NDIS_PACKET_TYPE_DIRECTED
12943981317546:   NDIS_PACKET_TYPE_MULTICAST
12943981317546:   NDIS_PACKET_TYPE_BROADCAST
12943981320703: XenNet     (BUFFER_TOO_SHORT 152 > 0)
12943981320843: Get Unknown OID 0x10117
12943981367468: XenPCI --> XenPci_EvtDeviceUsageNotification
12943981375984: XenPCI     notification_type = Paging, flag = 1
12943981375984: XenPCI <-- XenPci_EvtDeviceUsageNotification
12943981376000: XenPCI --> XenPciPdo_EvtDeviceUsageNotification
12943981376015: XenPCI     path = device/vbd/768
12943981376015: XenPCI     notification_type = Paging, flag = 1
12943981376921: XenPCI <-- XenPciPdo_EvtDeviceUsageNotification
12943981394609: XenPCI --> XenPci_EvtDeviceUsageNotification
12943981394625: XenPCI     notification_type = Dump, flag = 1
12943981394625: XenPCI <-- XenPci_EvtDeviceUsageNotification
12943981394656: XenPCI --> XenPciPdo_EvtDeviceUsageNotification
12943981394765: XenPCI     path = device/vbd/768
12943981394843: XenPCI     notification_type = Dump, flag = 1
12943981394890: XenPCI <-- XenPciPdo_EvtDeviceUsageNotification
12943981403531: XenPCI --> XenPci_EvtDeviceUsageNotification
12943981407312: XenVbd     WARNING: SRB completion time 7296ms
12943981408562: XenVbd     WARNING: SRB completion time 7031ms
12943981408640: XenPCI     notification_type = Paging, flag = 1
12943981408703: XenPCI <-- XenPci_EvtDeviceUsageNotification
12943981408703: XenPCI --> XenPciPdo_EvtDeviceUsageNotification
12943981408703: XenPCI     path = device/vbd/768
12943981408703: XenPCI     notification_type = Paging, flag = 1
12943981408703: XenPCI <-- XenPciPdo_EvtDeviceUsageNotification
12943981439781: XenVbd     WARNING: SRB completion time 5218ms
12943981464718: XenVbd     WARNING: SRB completion time 10593ms
12943981464843: XenVbd     WARNING: SRB completion time 10031ms
12943981465031: XenVbd     WARNING: SRB completion time 8796ms
12943981494734: XenVbd     WARNING: SRB completion time 5703ms
12943981494734: XenVbd     WARNING: SRB completion time 5703ms
12943981494734: XenVbd     WARNING: SRB completion time 5703ms
12943981494734: XenVbd     WARNING: SRB completion time 5703ms
12943981503484: XenVbd     WARNING: SRB completion time 5453ms
12943981503484: XenVbd     WARNING: SRB completion time 5546ms
12943981507921: XenNet     (BUFFER_TOO_SHORT 152 > 0)
12943981519562: XenVbd     WARNING: SRB completion time 9812ms
12943981531843:      Set OID_802_3_MULTICAST_LIST
12943981531843:        Length = 6
12943981533281:        Entries = 1
12943981536265: Set Unknown OID 0x10118
12943981536265: Set Unknown OID 0xfd010103
12943981536265: Set Unknown OID 0xfd010103
12943981536265:      Set OID_802_3_MULTICAST_LIST
12943981536265:        Length = 12
12943981536265:        Entries = 2
12943981560968: XenVbd     WARNING: SRB completion time 5359ms
12943981569890: XenVbd     WARNING: SRB completion time 5359ms
12943981570109: XenVbd     WARNING: SRB completion time 5359ms
12943981586093: XenVbd     WARNING: SRB completion time 6859ms
12943981586093: XenVbd     WARNING: SRB completion time 6406ms
12943981586265: XenVbd     WARNING: SRB completion time 6390ms
12943981586265: XenVbd     WARNING: SRB completion time 6093ms
12943981623781: XenVbd     WARNING: SRB completion time 5312ms
12943981625140: XenVbd     WARNING: SRB completion time 5312ms
12943981625140: XenVbd     WARNING: SRB completion time 5312ms
12943981625140: XenVbd     WARNING: SRB completion time 5312ms
12943981635078: XenVbd     WARNING: SRB completion time 6515ms
12943981641437: XenVbd     WARNING: SRB completion time 6515ms
12943981641484: XenVbd     WARNING: SRB completion time 6500ms
12943981642687: XenVbd     WARNING: SRB completion time 7031ms
12943981686593: Set Unknown OID 0xfd010103
12943981698343: XenPCI --> XenPci_EvtDeviceFileCreate
12943981698343: XenPCI --> XenBus_DeviceFileInit
12943981698359: XenPCI <-- XenBus_DeviceFileInit
12943981698375: XenPCI <-- XenPci_EvtDeviceFileCreate
12943981699343: XenPCI --> XenPci_EvtIoDefault
12943981699343: XenPCI --> XenBus_EvtIoWrite
12943981699359: XenPCI     35 bytes of write buffer remaining
12943981701734: XenPCI --> XenPci_IoWatch
12943981701734: XenPCI     completing request with length 35
12943981701734: XenPCI     no pending read (8000001a)
12943981703843: XenPCI <-- XenBus_EvtIoWrite
12943981704000: XenPCI <-- XenPci_IoWatch
12943981704000: XenPCI <-- XenPci_EvtIoDefault
12943981704062: XenPCI --> XenPci_EvtIoDefault
12943981706750: XenVbd     WARNING: SRB completion time 5015ms
12943981706765: XenPCI --> XenBus_EvtIoRead
12943981706765: XenPCI     found pending read
12943981706937: XenPCI <-- XenBus_ProcessReadRequest
12943981706953: XenPCI <-- XenBus_EvtIoRead
12943981706968: XenPCI <-- XenPci_EvtIoDefault
12943981706968: XenPCI --> XenPci_EvtIoDefault
12943981706968: XenPCI --> XenBus_EvtIoRead
12943981706984: XenPCI     no data to read
12943981706984: XenPCI <-- XenBus_EvtIoRead
12943981706984: XenPCI <-- XenPci_EvtIoDefault
12943981732328: XenVbd     WARNING: SRB completion time 5484ms
12943981732343: XenVbd     WARNING: SRB completion time 5500ms
12943981812359: XenVbd --> XenVbd_HwScsiResetBus
12943981812375: XenVbd     IRQL = 9
12943981812375: XenVbd     Completing in-flight srb 893B972C with status SRB_STATUS_BUS_RESET
12943981814640: XenVbd     Completing in-flight srb 893A96AC with status SRB_STATUS_BUS_RESET
12943981814656: XenVbd     Completing in-flight srb 893C4454 with status SRB_STATUS_BUS_RESET
12943981817187: XenVbd     Completing in-flight srb 893B44AC with status SRB_STATUS_BUS_RESET
12943981818187: XenVbd     Completing in-flight srb 8935922C with status SRB_STATUS_BUS_RESET
12943981818187: XenVbd     Completing in-flight srb 89359704 with status SRB_STATUS_BUS_RESET
12943981818187: XenVbd     Completing in-flight srb 893F3B84 with status SRB_STATUS_BUS_RESET
12943981818203: XenVbd     Completing in-flight srb 8937AD9C with status SRB_STATUS_BUS_RESET
12943981818421: XenVbd     Completing in-flight srb 89397FB4 with status SRB_STATUS_BUS_RESET
12943981818421: XenVbd <-- XenVbd_HwScsiResetBus
12943981818656: XenVbd     discarding reset shadow
12943981818656: XenVbd     discarding reset shadow
12943981818656: XenVbd     discarding reset shadow
12943981818656: XenVbd     discarding reset shadow
12943981818671: XenVbd     discarding reset shadow
12943981818687: XenVbd     discarding reset shadow
12943981818953: XenVbd     discarding reset shadow
12943981818968: XenVbd     discarding reset shadow
12943981818968: XenVbd     discarding reset shadow
12943981846156: XenVbd     WARNING: SRB completion time 5796ms
12943981846765: XenVbd     WARNING: SRB completion time 5875ms
12943981847500: XenVbd     WARNING: SRB completion time 5875ms
12943981847828: XenVbd     WARNING: SRB completion time 5750ms
12943981847828: XenVbd     WARNING: SRB completion time 5750ms
12943981848859: XenVbd     WARNING: SRB completion time 5750ms
12943981870437: XenVbd     WARNING: SRB completion time 13531ms
12943981870953: XenVbd     WARNING: SRB completion time 13531ms
12943981871078: XenVbd     WARNING: SRB completion time 13531ms
12943981871078: XenVbd     WARNING: SRB completion time 13531ms
12943981871093: XenVbd     WARNING: SRB completion time 13531ms
12943981871093: XenVbd     WARNING: SRB completion time 13531ms
12943981874562: XenVbd     WARNING: SRB completion time 13531ms
12943981874578: XenVbd     WARNING: SRB completion time 7984ms
12943981946562: XenVbd     WARNING: SRB completion time 5125ms
12943981946625: XenVbd     WARNING: SRB completion time 5125ms
12943981946796: XenVbd     WARNING: SRB completion time 5125ms
12943981946796: XenVbd     WARNING: SRB completion time 5125ms
12943981981015: XenVbd     WARNING: SRB completion time 5687ms
12943981981484: XenVbd     WARNING: SRB completion time 5593ms
12943982058968: XenVbd     WARNING: SRB completion time 7703ms
12943982059328: XenVbd     WARNING: SRB completion time 7703ms
12943982059328: XenVbd     WARNING: SRB completion time 7625ms
12943982059359: XenVbd     WARNING: SRB completion time 7703ms
12943982144203: XenVbd     WARNING: SRB completion time 5484ms
12943982144562: XenVbd     WARNING: SRB completion time 5484ms
12943982144906: XenVbd     WARNING: SRB completion time 5296ms
12943982155812: XenVbd     WARNING: SRB completion time 5890ms
12943982155937: XenVbd     WARNING: SRB completion time 5984ms
12943982678500: XenVbd --> XenVbd_HwScsiResetBus
12943982678500: XenVbd     IRQL = 9
12943982678500: XenVbd     Completing in-flight srb 89A63FB4 with status SRB_STATUS_BUS_RESET
12943982678500: XenVbd     Completing in-flight srb 893E966C with status SRB_STATUS_BUS_RESET
12943982678500: XenVbd     Completing in-flight srb 893EAF34 with status SRB_STATUS_BUS_RESET
12943982678515: XenVbd     Completing in-flight srb 893EB7EC with status SRB_STATUS_BUS_RESET
12943982678515: XenVbd     Completing in-flight srb 893EB0B4 with status SRB_STATUS_BUS_RESET
12943982678515: XenVbd     Completing in-flight srb 893E9984 with status SRB_STATUS_BUS_RESET
12943982678531: XenVbd     Completing in-flight srb 8994B75C with status SRB_STATUS_BUS_RESET
12943982678531: XenVbd     Completing in-flight srb 893EC86C with status SRB_STATUS_BUS_RESET
12943982678531: XenVbd <-- XenVbd_HwScsiResetBus
12943982693500: XenVbd --> XenVbd_HwScsiResetBus
12943982693500: XenVbd     IRQL = 9
12943982693500: XenVbd     Completing in-flight srb 893E9984 with status SRB_STATUS_BUS_RESET
12943982693500: XenVbd     Completing in-flight srb 893EAF34 with status SRB_STATUS_BUS_RESET
12943982693500: XenVbd     Completing in-flight srb 89A63FB4 with status SRB_STATUS_BUS_RESET
12943982693500: XenVbd     Completing in-flight srb 893EC86C with status SRB_STATUS_BUS_RESET
12943982693515: XenVbd     Completing in-flight srb 893EB0B4 with status SRB_STATUS_BUS_RESET
12943982693515: XenVbd     Completing in-flight srb 898363B4 with status SRB_STATUS_BUS_RESET
12943982693515: XenVbd     Completing in-flight srb 893EB7EC with status SRB_STATUS_BUS_RESET
12943982693515: XenVbd     Completing in-flight srb 893E966C with status SRB_STATUS_BUS_RESET
12943982693515: XenVbd     Completing in-flight srb 8994B75C with status SRB_STATUS_BUS_RESET
12943982693515: XenVbd <-- XenVbd_HwScsiResetBus
12943982708500: XenVbd --> XenVbd_HwScsiResetBus
12943982708500: XenVbd     IRQL = 9
12943982708500: XenVbd     Completing in-flight srb 8994B75C with status SRB_STATUS_BUS_RESET
12943982708500: XenVbd     Completing in-flight srb 89A63FB4 with status SRB_STATUS_BUS_RESET
12943982708500: XenVbd     Completing in-flight srb 893EC86C with status SRB_STATUS_BUS_RESET
12943982708500: XenVbd     Completing in-flight srb 893EB7EC with status SRB_STATUS_BUS_RESET
12943982708500: XenVbd     Completing in-flight srb 893EB0B4 with status SRB_STATUS_BUS_RESET
12943982708515: XenVbd     Completing in-flight srb 893E9984 with status SRB_STATUS_BUS_RESET
12943982708515: XenVbd     Completing in-flight srb 893E966C with status SRB_STATUS_BUS_RESET
12943982708515: XenVbd     Completing in-flight srb 898363B4 with status SRB_STATUS_BUS_RESET
12943982708515: XenVbd     Completing in-flight srb 893EAF34 with status SRB_STATUS_BUS_RESET
12943982708515: XenVbd <-- XenVbd_HwScsiResetBus
12943982722500: XenVbd --> XenVbd_HwScsiResetBus
12943982722500: XenVbd     IRQL = 9
12943982722500: XenVbd     Completing in-flight srb 893EB0B4 with status SRB_STATUS_BUS_RESET
12943982722500: XenVbd     Completing in-flight srb 8994B75C with status SRB_STATUS_BUS_RESET
12943982722500: XenVbd     Completing in-flight srb 893EAF34 with status SRB_STATUS_BUS_RESET
12943982722500: XenVbd     Completing in-flight srb 893EB7EC with status SRB_STATUS_BUS_RESET
12943982722515: XenVbd     Completing in-flight srb 893E9984 with status SRB_STATUS_BUS_RESET
12943982722515: XenVbd     Completing in-flight srb 893E966C with status SRB_STATUS_BUS_RESET
12943982722515: XenVbd <-- XenVbd_HwScsiResetBus
12943982736500: XenVbd --> XenVbd_HwScsiResetBus
12943982736500: XenVbd     IRQL = 9
12943982736500: XenVbd     completing queued SRB 89A63FB4 with status SRB_STATUS_BUS_RESET
12943982736500: XenVbd <-- XenVbd_HwScsiResetBus
12943982750500: XenVbd --> XenVbd_HwScsiResetBus
12943982750500: XenVbd     IRQL = 9
12943982750500: XenVbd     completing queued SRB 893EC86C with status SRB_STATUS_BUS_RESET
12943982750500: XenVbd <-- XenVbd_HwScsiResetBus
12943982751562: XenVbd --> DriverEntry
12943982751562: XenVbd     IRQL = 31
12943982751562: XenVbd     DriverObject = 00000000, RegistryPath = 00000000
12943982751562: XenVbd --> XenVbd_HwScsiFindAdapter
12943982751562: XenVbd     IRQL = 31
12943982751562: XenVbd     xvdd = 892C6300
12943982751562: XenVbd     BusInterruptLevel = 28
12943982751562: XenVbd     BusInterruptVector = 01c
12943982751562: XenVbd     NumberOfAccessRanges = 1
12943982751562: XenVbd     RangeStart = 1f3a2000, RangeLength = 00001000
12943982751562: XenVbd     XEN_INIT_TYPE_VECTORS
12943982751562: XenVbd     XEN_INIT_TYPE_DEVICE_STATE - 899B53CC
12943982751562: XenVbd     XEN_INIT_TYPE_RING - ring-ref = 89A9E000
12943982751562: XenVbd     XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 7
12943982751562: XenVbd     cached_use_other = 1
12943982751562: XenVbd     XEN_INIT_TYPE_READ_STRING - device-type = disk
12943982751562: XenVbd     device-type = Disk
12943982751562: XenVbd     XEN_INIT_TYPE_READ_STRING - mode = w
12943982751562: XenVbd     mode = w
12943982751562: XenVbd     XEN_INIT_TYPE_READ_STRING - sectors = 104857600
12943982751562: XenVbd     XEN_INIT_TYPE_READ_STRING - sector-size = 512
12943982751562: XenVbd     XEN_INIT_TYPE_GRANT_ENTRIES - entries = 11
12943982751562: XenVbd     qemu_hide_flags_value = 3
12943982751562: XenVbd     aligned_buffer_data = 892C857C
12943982751562: XenVbd     aligned_buffer = 892C9000
12943982751562: XenVbd     ConfigInfo->MaximumTransferLength = 4096
12943982751562: XenVbd     ConfigInfo->NumberOfPhysicalBreaks = 0
12943982751562: XenVbd     ConfigInfo->CachesData was initialised to 0
12943982751562: XenVbd     Dma64BitAddresses not supported
12943982751562: XenVbd <-- XenVbd_HwScsiFindAdapter
12943982751562: XenVbd --> XenVbd_HwScsiInitialize
12943982751562: XenVbd     IRQL = 31
12943982751562: XenVbd     dump_mode = 1
12943982751562: XenVbd <-- XenVbd_HwScsiInitialize
12943982751562: XenVbd     Command = INQUIRY
12943982751562: XenVbd --> XenVbd_HwScsiResetBus
12943982751562: XenVbd     IRQL = 31
12943982751562: XenVbd <-- XenVbd_HwScsiResetBus
12943982751562: XenVbd     Command = SCSIOP_START_STOP_UNIT
12943982751562: XenVbd     Command = READ_CAPACITY
12943982751562: XenVbd <-- DriverEntry
12943982751562: XenVbd     max_dump_mode_blocks = 8
12943982751562: XenVbd     max_dump_mode_length = 4096
12943982751562: 
*** Assertion failed: srb != NULL
***   Source File: e:\download\win-pvdrivers.hg\xenvbd\xenvbd_scsiport.c, line 1017

12943982751562: XenNet --> XenNet_Shutdown
12943982751562: XenNet <-- XenNet_Shutdown
XenPCI     Bug check 0x0000008E (0x80000003, 0x80878113, 0xB9FB4DD0, 0x00000000)

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

RE: [GIT/PATCH 0/5] Re: unfair servicing of DomU vbd requests

[James Harper]

> 
> I go through the patch, since all its changes happens inside
> __xen_evtchn_do_upcall(),
> so I apply the patch into my 2.6.31.kernel by manual. (I was failed to
merge a
> usable,
> 2.6.38dom0, since quite a lot branch needed, such as blkback, netback)
> 
> But still, the blue screen shows up. Log attached.
> Is the timeout better than before?
> 
> Beside, I think I need find some to examine my harddisk.
> 

Looking at the resets, every time you see "Completing in-flight srb ...
with status SRB_STATUS_BUS_RESET" you should subsequently see
"discarding reset shadow" indicating that Dom0 completed the request
also (even though we already told Windows that the reset was done). You
can see this after the first HwScsiResetBus, but not after any
subsequent resets, indicating that even after 72 seconds xenvbd hasn't
processed any further vbd requests. The last two requests confirm this
as no requests have been placed on the ring which must be full. That
says to me that either there is a bug in GPLPV, Dom0 still isn't
servicing IO requests fairly, or you do have a problem with your disk.

If it's a disk problem, you should be getting errors under Linux at some
level. If the drivers support SMART you can query their health that way
too.

James

RE: [GIT/PATCH 0/5] Re: unfair servicing of DomU vbd requests

[MaoXiaoyun]

[-- Attachment #1.1: Type: text/plain, Size: 2013 bytes --]


Thanks James.
Patch applied and crash log attached.
 
I've been able to merge the code accrording to Ian post on
http://lists.colo.xensource.com/archives/html/xen-devel/2011-03/msg00225.html
 
But unfortunately, the starting of 24HVMS become rather slow, and 
after some period of time, whole Host stop responding.
It takes some more time to find what is going on.

 
> Subject: RE: [GIT/PATCH 0/5] Re: [Xen-devel] unfair servicing of DomU vbd requests
> Date: Tue, 8 Mar 2011 22:04:42 +1100
> From: james.harper@bendigoit.com.au
> To: tinnycloud@hotmail.com
> 
> > 
> > Hi James.
> > 
> > I go through the patch, since all its changes happens inside
> > __xen_evtchn_do_upcall(),
> > so I apply the patch into my 2.6.31.kernel by manual. (I was failed to
> merge a
> > usable,
> > 2.6.38dom0, since quite a lot branch needed, such as blkback, netback)
> > 
> > But still, the blue screen shows up. Log attached.
> > Is the timeout better than before?
> > 
> > Beside, I think I need find some to examine my harddisk.
> > 
> 
> Not really important, but the ASSERT you are seeing in dump mode happens
> when xenvbd finally does complete the request, but obviously dump mode
> knows nothing about it. The following patch initialises the reset flag
> on all requests in dump mode so that when they do come back they are
> just discarded. Crash dump should now complete (although slowly in your
> case!):
> 
> diff -r 4722ecc909c3 xenvbd/xenvbd_scsiport.c
> --- a/xenvbd/xenvbd_scsiport.c Thu Mar 03 23:21:10 2011 +1100
> +++ b/xenvbd/xenvbd_scsiport.c Tue Mar 08 22:01:57 2011 +1100
> @@ -278,6 +278,12 @@
> {
> xvdd->shadows[i].req.id = i;
> put_shadow_on_freelist(xvdd, &xvdd->shadows[i]);
> + if (dump_mode)
> + {
> + /* set reset = TRUE to pick up in-flight requests when dump
> mode kicked in */
> + /* do it after put_shadow_on_freelist because that resets the
> reset flag */
> + xvdd->shadows[i].reset = TRUE;
> + }
> }
> }
> 
> James
 		 	   		  

[-- Attachment #1.2: Type: text/html, Size: 2669 bytes --]

[-- Attachment #2: qemu-dm-w3.MR_cp10.vhd.log --]
[-- Type: text/plain, Size: 59073 bytes --]

domid: 63
Watching /local/domain/0/device-model/63/logdirty/cmd
Watching /local/domain/0/device-model/63/command
char device redirected to /dev/pts/10
qemu_map_cache_init nr_buckets = 10000 size 4194304
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = d50e2fe3-9e00-ae05-56b7-e7b80d1fe141
Time offset set 0
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
xs_read(/local/domain/0/device-model/63/xen_extended_power_mgmt): read error
xs_read(): vncpasswd get error. /vm/d50e2fe3-9e00-ae05-56b7-e7b80d1fe141/vncpasswd.
Log-dirty: no command yet.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
xs_read(/local/domain/63/log-throttling): read error
qemu: ignoring not-understood drive `/local/domain/63/log-throttling'
medium change watch on `/local/domain/63/log-throttling' - unknown device, ignored
cirrus vga map change while on lfb mode
mapping vram to f0000000 - f0400000
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state.
12944114108718: XenPCI <-- XenPci_HighSyncCallFunctionN
12944114108718: XenPCI <-- XenPci_HighSyncCallFunction0
12944114108718: XenPCI     Waiting for highsync_complete_event
12944114108812: XenPCI <-- XenPci_HighSync
12944114108812: XenPCI --> XenPci_InitialBalloonDown
12944114108812: XenPCI     base = 0x40000000, Xen Signature = XenVMMXenVMM, EAX = 0x40000003
12944114108828: XenPCI     Hypercall area at 89DB5000
12944114108843: XenPCI     XENMEM_maximum_reservation = 525312
12944114108843: XenPCI     XENMEM_current_reservation = 131288
12944114108843: XenPCI     Trying to give 1540 MB to Xen
12944114124187: XenPCI <-- XenPci_InitialBalloonDown
12944114124187: XenPCI     KeInitializeCrashDumpHeader status = 00000000, size = 4096
12944114124187: XenPCI GPLPV 0.10.0.0
12944114124437: XenPCI --> XenPci_FixLoadOrder
12944114124453: XenPCI     dummy_group_index = 1
12944114124453: XenPCI     wdf_load_group_index = 2
12944114124453: XenPCI     xenpci_group_index = 3
12944114124453: XenPCI     boot_bus_extender_index = 4
12944114124468: XenPCI <-- XenPci_FixLoadOrder
12944114124468: XenPCI     Version = 1
Unknown PV product 2 loaded in guest
PV driver build 1
12944114124468: XenPCI     Disabled qemu devices 03
12944114124484: XenPCI <-- DriverEntry
12944114155312: XenPCI     Xen PCI device found - must be fdo
12944114155406: XenPCI --> XenPci_EvtDeviceAdd_XenPci
12944114155421: XenPCI <-- XenPci_EvtDeviceAdd_XenPci
12944114155578: XenPCI --> XenPci_EvtDevicePrepareHardware
12944114155609: XenPCI     IoPort Address(c000) Length: 256
12944114155609: XenPCI     Private Data: 0x01 0x00 0x00
12944114155609: XenPCI     Memory mapped CSR:(f2000000:0) Length:(16777216)
12944114155609: XenPCI     Memory flags = 0004
12944114155625: XenPCI     Private Data: 0x01 0x01 0x00
12944114155890: XenPCI     irq_number = 01c
12944114156250: XenPCI     irq_vector = 1a3
12944114156250: XenPCI     irq_level = 009
12944114156250: XenPCI     irq_mode = LevelSensitive
12944114156265: XenPCI     ShareDisposition = CmResourceShareShared
12944114156265: XenPCI <-- XenPci_EvtDevicePrepareHardware
12944114156265: XenPCI --> XenPci_EvtDeviceD0Entry
12944114156265: XenPCI     WdfPowerDeviceD3Final
12944114156437: XenPCI --> XenPci_Init
12944114156437: XenPCI     base = 0x40000000, Xen Signature = XenVMMXenVMM, EAX = 0x40000003
12944114156453: XenPCI     Hypercall area at 89B62000
12944114156484: XenPCI     shared_info_area_unmapped.QuadPart = f2000000
12944114156687: XenPCI     gpfn = f2000
12944114156687: XenPCI     hypervisor memory op (XENMAPSPACE_shared_info) ret = 0
12944114156796: XenPCI <-- XenPci_Init
12944114156875: XenPCI --> GntTbl_Init
12944114156890: XenPCI     grant_frames = 32
12944114156890: XenPCI     grant_entries = 16384
12944114156906: XenPCI     pfn = 99a9
12944114156906: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99a9
12944114156906: XenPCI     decreased 1 pages for grant table frame 0
12944114157828: XenPCI     pfn = 99aa
12944114158234: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99aa
12944114158343: XenPCI     decreased 1 pages for grant table frame 1
12944114158343: XenPCI     pfn = 99ab
12944114158359: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99ab
12944114158359: XenPCI     decreased 1 pages for grant table frame 2
12944114158375: XenPCI     pfn = 99ac
12944114159343: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99ac
12944114159343: XenPCI     decreased 1 pages for grant table frame 3
12944114159359: XenPCI     pfn = 99ad
12944114159359: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99ad
12944114159359: XenPCI     decreased 1 pages for grant table frame 4
12944114159359: XenPCI     pfn = 99ae
12944114159406: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99ae
12944114159421: XenPCI     decreased 1 pages for grant table frame 5
12944114159562: XenPCI     pfn = 99af
12944114159625: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99af
12944114159625: XenPCI     decreased 1 pages for grant table frame 6
12944114159625: XenPCI     pfn = 99b0
12944114159625: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99b0
12944114159625: XenPCI     decreased 1 pages for grant table frame 7
12944114162328: XenPCI     pfn = 99b1
12944114162343: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99b1
12944114162359: XenPCI     decreased 1 pages for grant table frame 8
12944114162406: XenPCI     pfn = 99b2
12944114162406: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99b2
12944114162406: XenPCI     decreased 1 pages for grant table frame 9
12944114162468: XenPCI     pfn = 99b3
12944114162468: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99b3
12944114162468: XenPCI     decreased 1 pages for grant table frame 10
12944114162468: XenPCI     pfn = 99b4
12944114162468: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99b4
12944114162484: XenPCI     decreased 1 pages for grant table frame 11
12944114162484: XenPCI     pfn = 99b5
12944114162484: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99b5
12944114163937: XenPCI     decreased 1 pages for grant table frame 12
12944114163937: XenPCI     pfn = 99b6
12944114163937: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99b6
12944114163937: XenPCI     decreased 1 pages for grant table frame 13
12944114163937: XenPCI     pfn = 99b7
12944114163937: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99b7
12944114163953: XenPCI     decreased 1 pages for grant table frame 14
12944114164125: XenPCI     pfn = 99b8
12944114164125: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99b8
12944114164125: XenPCI     decreased 1 pages for grant table frame 15
12944114164203: XenPCI     pfn = 99b9
12944114164203: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99b9
12944114164203: XenPCI     decreased 1 pages for grant table frame 16
12944114164203: XenPCI     pfn = 99ba
12944114164218: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99ba
12944114164218: XenPCI     decreased 1 pages for grant table frame 17
12944114164218: XenPCI     pfn = 99bb
12944114164218: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99bb
12944114164218: XenPCI     decreased 1 pages for grant table frame 18
12944114164218: XenPCI     pfn = 99bc
12944114164218: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99bc
12944114164218: XenPCI     decreased 1 pages for grant table frame 19
12944114164437: XenPCI     pfn = 99bd
12944114164437: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99bd
12944114164437: XenPCI     decreased 1 pages for grant table frame 20
12944114164437: XenPCI     pfn = 99be
12944114164531: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99be
12944114164531: XenPCI     decreased 1 pages for grant table frame 21
12944114164593: XenPCI     pfn = 99bf
12944114164625: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99bf
12944114164625: XenPCI     decreased 1 pages for grant table frame 22
12944114164640: XenPCI     pfn = 99c0
12944114164781: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99c0
12944114164781: XenPCI     decreased 1 pages for grant table frame 23
12944114164812: XenPCI     pfn = 99c1
12944114164812: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99c1
12944114164828: XenPCI     decreased 1 pages for grant table frame 24
12944114164937: XenPCI     pfn = 99c2
12944114164937: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99c2
12944114165265: XenPCI     decreased 1 pages for grant table frame 25
12944114165281: XenPCI     pfn = 99c3
12944114165281: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99c3
12944114165328: XenPCI     decreased 1 pages for grant table frame 26
12944114165515: XenPCI     pfn = 99c4
12944114165515: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99c4
12944114165515: XenPCI     decreased 1 pages for grant table frame 27
12944114165625: XenPCI     pfn = 99c5
12944114165625: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99c5
12944114165625: XenPCI     decreased 1 pages for grant table frame 28
12944114165625: XenPCI     pfn = 99c6
12944114165640: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99c6
12944114165640: XenPCI     decreased 1 pages for grant table frame 29
12944114165843: XenPCI     pfn = 99c7
12944114165937: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99c7
12944114165937: XenPCI     decreased 1 pages for grant table frame 30
12944114165953: XenPCI     pfn = 99c8
12944114165953: XenPCI     Calling HYPERVISOR_memory_op - pfn = 99c8
12944114165953: XenPCI     decreased 1 pages for grant table frame 31
12944114166031: XenPCI --> GntTbl_Map
12944114166296: XenPCI <-- GntTbl_Map
12944114166296: XenPCI <-- GntTbl_Init
12944114166296: XenPCI --> EvtChn_Init
12944114166296: XenPCI --> _hvm_set_parameter
12944114166546: XenPCI HYPERVISOR_hvm_op retval = 0
12944114166562: XenPCI <-- _hvm_set_parameter
12944114166812: XenPCI     hvm_set_parameter(HVM_PARAM_CALLBACK_IRQ, 28) = 0
12944114166812: XenPCI --> EvtChn_AllocIpi
12944114166812: XenPCI <-- EvtChn_AllocIpi
12944114166812: XenPCI --> EvtChn_BindDpc
12944114167078: XenPCI <-- EvtChn_BindDpc
12944114167078: XenPCI     pdo_event_channel = 5
12944114167078: XenPCI <-- EvtChn_Init
12944114167078: XenPCI <-- XenPci_EvtDeviceD0Entry
12944114167125: XenPCI --> EvtChn_EvtInterruptEnable
12944114167859: XenPCI <-- EvtChn_EvtInterruptEnable
12944114167921: XenPCI --> XenPci_EvtDeviceD0EntryPostInterruptsEnabled
12944114167937: XenPCI --> XenBus_Init
12944114167937: XenPCI --> _hvm_get_parameter
12944114167937: XenPCI HYPERVISOR_hvm_op retval = 0
12944114167937: XenPCI <-- _hvm_get_parameter
12944114167937: XenPCI --> _hvm_get_parameter
12944114167937: XenPCI HYPERVISOR_hvm_op retval = 0
12944114167937: XenPCI <-- _hvm_get_parameter
12944114167937: XenPCI --> EvtChn_BindDpc
12944114167937: XenPCI <-- EvtChn_BindDpc
12944114167953: XenPCI <-- XenBus_Init
12944114167953: XenPCI     suspend event channel = 6
12944114168062: XenPCI --> EvtChn_BindDpc
12944114169578: XenPCI <-- EvtChn_BindDpc
12944114169593: XenPCI --> XenPci_SysrqHandler
12944114169625: XenPCI     SysRq Value = (null)
12944114169625: XenPCI <-- XenPci_SysrqHandler
12944114169625: XenPCI --> XenPci_ShutdownHandler
12944114169625: Error reading shutdown path - ENOENT
12944114169640: XenPCI <-- XenPci_ShutdownHandler
12944114169640: XenPCI --> XenPci_DeviceWatchHandler
12944114169640: XenPCI <-- XenPci_DeviceWatchHandler
12944114169640: XenPCI     Initial Memory Value = 512 (524288)
12944114169640: XenPCI --> XenPci_BalloonThreadProc
12944114169640: XenPCI <-- XenPci_EvtDeviceD0EntryPostInterruptsEnabled
12944114169640: XenPCI --> XenPci_BalloonHandler
12944114169640: XenPCI --> XenPci_EvtChildListScanForChildren
12944114169640: XenPCI     low_mem_event = 89D79D50, state = 0
12944114169656: XenPCI     target memory value = 512 (524288)
12944114169812: XenPCI     Found path = device/vbd/768
12944114175187: XenPCI     Found path = device/vif/0
12944114176406: XenPCI <-- XenPci_BalloonHandler
12944114176406: XenPCI <-- XenPci_EvtChildListScanForChildren
12944114176406: XenPCI     Got balloon event, current = 512, target = 512
12944114176421: XenPCI --> XenPci_EvtChildListCreateDevice
12944114176421: XenPCI     No change to memory
12944114176421: XenPCI     device = 'vbd', index = '768', path = 'device/vbd/768'
12944114176421: XenPCI <-- XenPci_EvtChildListCreateDevice
12944114176437: XenPCI --> XenPci_EvtChildListCreateDevice
12944114176437: XenPCI     device = 'vif', index = '0', path = 'device/vif/0'
12944114176437: XenPCI <-- XenPci_EvtChildListCreateDevice
12944114193359: XenVbd --> DriverEntry
12944114196250: XenVbd     IRQL = 0
12944114197687: XenVbd     DriverObject = 8992E968, RegistryPath = 80090BF8
12944114197703: XenVbd <-- DriverEntry
12944114197703: XenPCI --> XenPciPdo_EvtDeviceWdmIrpPreprocess_START_DEVICE
12944114197703: XenPCI     device/vbd/768
12944114197703: XenPCI     CmResourceTypeMemory (0)
12944114197718: XenPCI     Start = f2000000, Length = 0
12944114197718: XenPCI     pfn[0] = 0001f2df
12944114197718: XenPCI     New Start = 000000001f2df000, Length = 4096
12944114197734: XenPCI     CmResourceTypeMemory (1)
12944114197734: XenPCI     Start = f2000001, Length = 0
12944114197734: XenPCI <-- XenPciPdo_EvtDeviceWdmIrpPreprocess_START_DEVICE
12944114197750: XenPCI --> XenPciPdo_EvtDevicePrepareHardware
12944114197750: XenPCI <-- XenPciPdo_EvtDevicePrepareHardware
12944114197765: XenPCI --> XenPciPdo_EvtDeviceD0Entry
12944114197781: XenPCI     path = device/vbd/768
12944114200718: XenPCI     WdfPowerDeviceD3Final
12944114201515: XenPCI --> XenPci_GetBackendAndAddWatch
12944114201796: XenPCI <-- XenPci_GetBackendAndAddWatch
12944114201796: XenPCI --> XenPci_UpdateBackendState
12944114202484: XenPCI --> XenConfig_InitConfigPage
12944114202500: XenPCI     fdo_driver_object = 8992E968
12944114202500: XenPCI     fdo_driver_extension = 89944008
12944114202500: XenPCI <-- XenConfig_InitConfigPage
12944114202500: XenPCI --> XenPci_XenConfigDeviceSpecifyBuffers
12944114202500: XenPCI     XEN_INIT_TYPE_RING - ring-ref = 8993C000
12944114204859: XenPCI     XEN_INIT_TYPE_RING - ring-ref = 16383
12944114204859: XenPCI     Backend State Changed to InitWait
12944114204859: XenPCI <-- XenPci_UpdateBackendState
12944114204953: XenPCI --> XenPci_DeviceWatchHandler
12944114204953: XenPCI     XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 7
12944114204968: XenPCI <-- XenPci_DeviceWatchHandler
12944114205156: XenPCI --> EvtChn_BindIrq
12944114205156: XenPCI <-- EvtChn_BindIrq
12944114205156: XenPCI --> XenPci_ChangeFrontendStateMap
12944114205156: XenPCI --> XenPci_ChangeFrontendState
12944114205187: XenPCI --> XenPci_DeviceWatchHandler
12944114205265: XenPCI <-- XenPci_DeviceWatchHandler
12944114205265: XenPCI --> XenPci_DeviceWatchHandler
12944114205265: XenPCI <-- XenPci_DeviceWatchHandler
12944114206921: XenPCI --> XenPci_UpdateBackendState
12944114206921: XenPCI --> XenPci_UpdateBackendState
12944114211109: XenPCI     Backend State Changed to Connected
12944114211125: XenPCI <-- XenPci_UpdateBackendState
12944114211125: XenPCI     Still waiting for 4 (currently 4)...
12944114211265: XenPCI <-- XenPci_ChangeFrontendState
12944114211281: XenPCI <-- XenPci_ChangeFrontendStateMap
12944114211453: XenPCI     state unchanged
12944114211781: XenPCI --> XenPci_ChangeFrontendStateMap
12944114211796: XenPCI <-- XenPci_ChangeFrontendStateMap
12944114211796: XenPCI <-- XenPci_XenConfigDeviceSpecifyBuffers
12944114211796: XenPCI <-- XenPciPdo_EvtDeviceD0Entry
12944114212625: XenVbd --> XenVbd_HwScsiFindAdapter
12944114212625: XenVbd     IRQL = 0
12944114212625: XenVbd     xvdd = 898F2004
12944114212750: XenVbd     BusInterruptLevel = 28
12944114212796: XenVbd     BusInterruptVector = 01c
12944114212812: XenVbd     NumberOfAccessRanges = 1
12944114212812: XenVbd     RangeStart = 1f2df000, RangeLength = 00001000
12944114213765: XenVbd     XEN_INIT_TYPE_VECTORS
12944114213765: XenVbd     XEN_INIT_TYPE_DEVICE_STATE - 89AB29BC
12944114213765: XenVbd     XEN_INIT_TYPE_RING - ring-ref = 8993C000
12944114213765: XenVbd     XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 7
12944114213765: XenVbd     XEN_INIT_TYPE_READ_STRING - device-type = disk
12944114213781: XenVbd     device-type = Disk
12944114213781: XenVbd     XEN_INIT_TYPE_READ_STRING - mode = w
12944114213968: XenVbd     mode = w
12944114213968: XenVbd     XEN_INIT_TYPE_READ_STRING - sectors = 104857600
12944114213984: XenVbd     XEN_INIT_TYPE_READ_STRING - sector-size = 512
12944114213984: XenVbd     XEN_INIT_TYPE_GRANT_ENTRIES - entries = 11
12944114213984: XenVbd     qemu_hide_flags_value = 3
12944114214109: XenVbd     aligned_buffer_data = 898F4280
12944114215343: XenVbd     aligned_buffer = 898F5000
12944114215359: XenVbd     ConfigInfo->MaximumTransferLength = 45056
12944114215375: XenVbd     ConfigInfo->NumberOfPhysicalBreaks = 10
12944114215375: XenVbd     ConfigInfo->CachesData was initialised to 0
12944114216718: XenVbd     Dma64BitAddresses not supported
12944114216796: XenVbd <-- XenVbd_HwScsiFindAdapter
12944114224421: XenVbd --> XenVbd_HwScsiInitialize
12944114224953: XenVbd     IRQL = 9
12944114224953: XenVbd     dump_mode = 0
12944114224953: XenVbd <-- XenVbd_HwScsiInitialize
12944114224968: XenVbd --> XenVbd_HwScsiAdapterControl
12944114224968: XenVbd     ring_detect_state = 1, index = 0, operation = ff, id = 0, status = 0
12944114225046: XenVbd     req_prod = 2, rsp_prod = 2, rsp_cons = 0
12944114225062: XenVbd     ring_detect_state = 2, index = 1, operation = 0, id = ff, status = 0
12944114225062: XenVbd     req_prod = 2, rsp_prod = 2, rsp_cons = 0
12944114225062: XenVbd     switching to 'other' ring size
12944114225062: XenVbd     IRQL = 0
12944114225296: XenVbd     xvdd = 898F2004
12944114225296: XenVbd     ScsiQuerySupportedControlTypes (Max = 5)
12944114226484: XenVbd <-- XenVbd_HwScsiAdapterControl
12944114243046: XenVbd     SRB_FUNCTION_IO_CONTROL
12944114244406: XenVbd     SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 28, allocation_length = 192
12944114244406: XenVbd     EXECUTE_SCSI Command = 1A returned error 00
12944114244546: XenVbd     SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192
12944114265609: XenVbd     SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 12
12944114573703: XenVbd     WARNING: SRB completion time 7140ms
12944114666203: XenVbd     WARNING: SRB completion time 5296ms
12944114667343: XenVbd     WARNING: SRB completion time 5296ms
12944114667343: XenVbd     WARNING: SRB completion time 5296ms
12944114667343: XenVbd     WARNING: SRB completion time 5296ms
12944114670328: XenVbd     WARNING: SRB completion time 5296ms
12944114863234: XenVbd     WARNING: SRB completion time 5781ms
12944114883515: XenVbd     WARNING: SRB completion time 9421ms
12944115105671: XenNet --> DriverEntry
12944115105671: XenNet     DriverObject = 89A3DA08, RegistryPath = 89A56000
12944115105671: XenNet     NdisGetVersion = 50001
12944115105687: XenNet     ndis_wrapper_handle = 00000000
12944115105687: XenNet     ndis_wrapper_handle = 89A3D958
12944115105703: XenNet     NdisMInitializeWrapper succeeded
12944115105703: XenNet     MajorNdisVersion = 5,  MinorNdisVersion = 1
12944115105703: XenNet     about to call NdisMRegisterMiniport
12944115105703: XenNet     called NdisMRegisterMiniport
12944115105703: XenNet <-- DriverEntry
12944115106546: XenPCI --> XenPciPdo_EvtDeviceWdmIrpPreprocess_START_DEVICE
12944115106546: XenPCI     device/vif/0
12944115106546: XenPCI     CmResourceTypeMemory (0)
12944115106546: XenPCI     Start = f2000000, Length = 0
12944115106546: XenPCI     pfn[0] = 0001f29f
12944115106546: XenPCI     New Start = 000000001f29f000, Length = 4096
12944115106546: XenPCI     CmResourceTypeMemory (1)
12944115106562: XenPCI     Start = f2000001, Length = 0
12944115106562: XenPCI <-- XenPciPdo_EvtDeviceWdmIrpPreprocess_START_DEVICE
12944115106562: XenPCI --> XenPciPdo_EvtDevicePrepareHardware
12944115106562: XenPCI <-- XenPciPdo_EvtDevicePrepareHardware
12944115106562: XenPCI --> XenPciPdo_EvtDeviceD0Entry
12944115106562: XenPCI     path = device/vif/0
12944115106562: XenPCI     WdfPowerDeviceD3Final
12944115106562: XenPCI --> XenPci_GetBackendAndAddWatch
12944115106562: XenPCI <-- XenPci_GetBackendAndAddWatch
12944115106562: XenPCI --> XenPci_UpdateBackendState
12944115106562: XenPCI --> XenConfig_InitConfigPage
12944115106578: XenPCI     fdo_driver_object = 89A3DA08
12944115106578: XenPCI     Backend State Changed to InitWait
12944115106578: XenPCI     fdo_driver_extension = 00000000
12944115106593: XenPCI <-- XenPci_UpdateBackendState
12944115106593: XenPCI     fdo_driver_object = 89D68490
12944115106593: XenPCI     fdo_driver_extension = 00000000
12944115106609: XenPCI <-- XenConfig_InitConfigPage
12944115106609: XenPCI --> XenPci_XenConfigDeviceSpecifyBuffers
12944115106609: XenPCI --> XenPci_ChangeFrontendStateMap
12944115106609: XenPCI <-- XenPci_ChangeFrontendStateMap
12944115106609: XenPCI --> XenPci_ChangeFrontendStateMap
12944115106625: XenPCI <-- XenPci_ChangeFrontendStateMap
12944115106625: XenPCI <-- XenPci_XenConfigDeviceSpecifyBuffers
12944115106625: XenPCI <-- XenPciPdo_EvtDeviceD0Entry
12944115106640: XenNet --> XenNet_Init
12944115106671: XenNet     IRQL = 0
12944115106671: XenNet     nrl_length = 40
12944115106671: XenNet     irq_vector = 01c, irq_level = 01c, irq_mode = NdisInterruptLevelSensitive
12944115106671: XenNet     XEN_INIT_TYPE_13
12944115106671: XenNet     XEN_INIT_TYPE_VECTORS
12944115106703: XenNet     XEN_INIT_TYPE_DEVICE_STATE - 8993AFB4
12944115106703: ScatterGather = 1
12944115106828: LargeSendOffload = 61440
12944115106828: ChecksumOffload = 1
12944115106828: ChecksumOffloadRxCheck = 1
12944115106828: MTU = 1500
12944115106828: RxInterruptModeration = 0
12944115106828: Could not read NetworkAddress value (c0000001) or value is invalid
12944115106828: XenNet --> XenNet_D0Entry
12944115106828: XenPCI --> XenPci_XenConfigDeviceSpecifyBuffers
12944115106828: XenPCI     XEN_INIT_TYPE_RING - tx-ring-ref = 897C8000
12944115106828: XenPCI     XEN_INIT_TYPE_RING - tx-ring-ref = 16306
12944115106843: XenPCI     XEN_INIT_TYPE_RING - rx-ring-ref = 89A23000
12944115106843: XenPCI --> XenPci_DeviceWatchHandler
12944115106843: XenPCI     XEN_INIT_TYPE_RING - rx-ring-ref = 16114
12944115106843: XenPCI <-- XenPci_DeviceWatchHandler
12944115106859: XenPCI --> XenPci_DeviceWatchHandler
12944115106859: XenPCI     XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 8
12944115106859: XenPCI <-- XenPci_DeviceWatchHandler
12944115106859: XenPCI --> EvtChn_Bind
12944115106859: XenPCI --> XenPci_DeviceWatchHandler
12944115106859: XenPCI <-- EvtChn_Bind
12944115106859: XenPCI <-- XenPci_DeviceWatchHandler
12944115106875: XenPCI --> XenPci_DeviceWatchHandler
12944115106875: XenPCI <-- XenPci_DeviceWatchHandler
12944115106875: XenPCI --> XenPci_DeviceWatchHandler
12944115106875: XenPCI <-- XenPci_DeviceWatchHandler
12944115106968: XenPCI --> XenPci_DeviceWatchHandler
12944115106984: XenPCI <-- XenPci_DeviceWatchHandler
12944115106984: XenPCI --> XenPci_ChangeFrontendStateMap
12944115106984: XenPCI --> XenPci_DeviceWatchHandler
12944115106984: XenPCI <-- XenPci_DeviceWatchHandler
12944115107000: XenPCI <-- XenPci_ChangeFrontendStateMap
12944115107000: XenPCI --> XenPci_DeviceWatchHandler
12944115107000: XenPCI <-- XenPci_DeviceWatchHandler
12944115107000: XenPCI --> XenPci_ChangeFrontendStateMap
12944115107000: XenPCI --> XenPci_ChangeFrontendState
12944115107015: XenPCI --> XenPci_DeviceWatchHandler
12944115107015: XenPCI <-- XenPci_DeviceWatchHandler
12944115107015: XenPCI --> XenPci_UpdateBackendState
12944115107015: XenPCI     Backend State Changed to Connected
12944115107015: XenPCI <-- XenPci_UpdateBackendState
12944115107031: XenPCI <-- XenPci_ChangeFrontendState
12944115107031: XenPCI <-- XenPci_ChangeFrontendStateMap
12944115107046: XenPCI <-- XenPci_XenConfigDeviceSpecifyBuffers
12944115107093: XenNet --> XenNet_ConnectBackend
12944115107109: XenNet     XEN_INIT_TYPE_13
12944115107109: XenNet     XEN_INIT_TYPE_VECTORS
12944115107109: XenNet     XEN_INIT_TYPE_DEVICE_STATE - 8993AFB4
12944115107109: XenNet     XEN_INIT_TYPE_RING - tx-ring-ref = 897C8000
12944115107140: XenNet     XEN_INIT_TYPE_RING - rx-ring-ref = 89A23000
12944115107140: XenNet     XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 8
12944115107140: XenNet     XEN_INIT_TYPE_READ_STRING - mac = 00:16:3e:ea:b1:b5
12944115107140: XenNet     XEN_INIT_TYPE_READ_STRING - feature-sg = 1
12944115107140: XenNet     XEN_INIT_TYPE_READ_STRING - feature-gso-tcpv4 = 1
12944115107156: XenNet     XEN_INIT_TYPE_17
12944115107156: XenNet <-- XenNet_ConnectBackend
12944115107156: XenNet --> XenNet_RxInit
12944115107156: XenNet <-- XenNet_RxInit
12944115107156: XenNet <-- XenNet_D0Entry
12944115107156: Get Unknown OID 0x10202
12944115107156: XenNet --> XenNet_PnPEventNotify
12944115107156: XenNet     NdisDevicePnPEventPowerProfileChanged
12944115107156: XenNet <-- XenNet_PnPEventNotify
12944115107453: Get Unknown OID 0x10201
12944115107484: Get Unknown OID 0xfc010210
12944115107484: Get OID_TCP_TASK_OFFLOAD
12944115107484: XenNet     (BUFFER_TOO_SHORT 100 > 28)
12944115107484: Get OID_TCP_TASK_OFFLOAD
12944115107484: config_csum enabled
12944115107515: nto = 895CC514
12944115107515: nto->Size = 24
12944115107515: nto->TaskBufferLength = 16
12944115107578: config_gso enabled
12944115107625: nto = 895CC538
12944115107625: nto->Size = 24
12944115107640: nto->TaskBufferLength = 16
12944115107640: &(nttls->IpOptions) = 895CC559
12944115107656: Set OID_TCP_TASK_OFFLOAD
12944115107656: TcpIpChecksumNdisTask
12944115107656:   V4Transmit.IpOptionsSupported  = 0
12944115107671:   V4Transmit.TcpOptionsSupported = 1
12944115107671:   V4Transmit.TcpChecksum         = 1
12944115107671:   V4Transmit.UdpChecksum         = 0
12944115107671:   V4Transmit.IpChecksum          = 0
12944115107671:   V4Receive.IpOptionsSupported   = 0
12944115107781:   V4Receive.TcpOptionsSupported  = 0
12944115107796:   V4Receive.TcpChecksum          = 1
12944115107812:   V4Receive.UdpChecksum          = 0
12944115107812:   V4Receive.IpChecksum           = 0
12944115107812:   V6Transmit.IpOptionsSupported  = 0
12944115107828:   V6Transmit.TcpOptionsSupported = 0
12944115107828:   V6Transmit.TcpChecksum         = 0
12944115107828:   V6Transmit.UdpChecksum         = 0
12944115107828:   V6Receive.IpOptionsSupported   = 0
12944115107843:   V6Receive.TcpOptionsSupported  = 0
12944115107843:   V6Receive.TcpChecksum          = 0
12944115107843:   V6Receive.UdpChecksum          = 0
12944115107843: TcpLargeSendNdisTask
12944115107843:   MaxOffLoadSize                 = 61440
12944115107843:   MinSegmentCount                = 4
12944115107843:   TcpOptions                     = 0
12944115107843:   IpOptions                      = 0
12944115107859: Get OID_PNP_CAPABILITIES
12944115107859: Set Unknown OID 0x10119
12944115107859: Set OID_GEN_CURRENT_LOOKAHEAD 128 (89A24000)
12944115107859: Set OID_GEN_CURRENT_PACKET_FILTER (xi = 89A24000)
12944115107859:   NDIS_PACKET_TYPE_DIRECTED
12944115107875:   NDIS_PACKET_TYPE_MULTICAST
12944115107875:   NDIS_PACKET_TYPE_BROADCAST
12944115125890: XenNet     (BUFFER_TOO_SHORT 152 > 0)
12944115125890: Get Unknown OID 0x10117
12944115217218: XenPCI --> XenPci_EvtDeviceUsageNotification
12944115217218: XenPCI     notification_type = Paging, flag = 1
12944115217234: XenPCI <-- XenPci_EvtDeviceUsageNotification
12944115217234: XenPCI --> XenPciPdo_EvtDeviceUsageNotification
12944115217234: XenPCI     path = device/vbd/768
12944115217234: XenPCI     notification_type = Paging, flag = 1
12944115217250: XenPCI <-- XenPciPdo_EvtDeviceUsageNotification
12944115224781: XenPCI --> XenPci_EvtDeviceUsageNotification
12944115224796: XenPCI     notification_type = Dump, flag = 1
12944115224796: XenPCI <-- XenPci_EvtDeviceUsageNotification
12944115224796: XenPCI --> XenPciPdo_EvtDeviceUsageNotification
12944115224796: XenPCI     path = device/vbd/768
12944115224796: XenPCI     notification_type = Dump, flag = 1
12944115224796: XenPCI <-- XenPciPdo_EvtDeviceUsageNotification
12944115234437: XenPCI --> XenPci_EvtDeviceUsageNotification
12944115234437: XenPCI     notification_type = Paging, flag = 1
12944115234437: XenPCI <-- XenPci_EvtDeviceUsageNotification
12944115234437: XenPCI --> XenPciPdo_EvtDeviceUsageNotification
12944115234437: XenPCI     path = device/vbd/768
12944115234453: XenPCI     notification_type = Paging, flag = 1
12944115234453: XenPCI <-- XenPciPdo_EvtDeviceUsageNotification
12944115256125: XenNet     (BUFFER_TOO_SHORT 152 > 0)
12944115258500:      Set OID_802_3_MULTICAST_LIST
12944115258500:        Length = 6
12944115258500:        Entries = 1
12944115271125: Set Unknown OID 0x10118
12944115271125: Set Unknown OID 0xfd010103
12944115271125: Set Unknown OID 0xfd010103
12944115271125:      Set OID_802_3_MULTICAST_LIST
12944115271140:        Length = 12
12944115271140:        Entries = 2
12944115277328: Set Unknown OID 0xfd010103
12944115277890: XenPCI --> XenPci_EvtDeviceFileCreate
12944115277890: XenPCI --> XenBus_DeviceFileInit
12944115277906: XenPCI <-- XenBus_DeviceFileInit
12944115277906: XenPCI <-- XenPci_EvtDeviceFileCreate
12944115277906: XenPCI --> XenPci_EvtIoDefault
12944115277906: XenPCI --> XenBus_EvtIoWrite
12944115277906: XenPCI     35 bytes of write buffer remaining
12944115277906: XenPCI --> XenPci_IoWatch
12944115277906: XenPCI     completing request with length 35
12944115277906: XenPCI     no pending read (8000001a)
12944115277906: XenPCI <-- XenBus_EvtIoWrite
12944115277921: XenPCI <-- XenPci_IoWatch
12944115277921: XenPCI <-- XenPci_EvtIoDefault
12944115277921: XenPCI --> XenPci_EvtIoDefault
12944115277921: XenPCI --> XenBus_EvtIoRead
12944115277937: XenPCI     found pending read
12944115277937: XenPCI <-- XenBus_ProcessReadRequest
12944115277937: XenPCI <-- XenBus_EvtIoRead
12944115277937: XenPCI <-- XenPci_EvtIoDefault
12944115277937: XenPCI --> XenPci_EvtIoDefault
12944115277937: XenPCI --> XenBus_EvtIoRead
12944115277937: XenPCI     no data to read
12944115277937: XenPCI <-- XenBus_EvtIoRead
12944115277953: XenPCI <-- XenPci_EvtIoDefault
12944115368953: XenVbd --> XenVbd_HwScsiResetBus
12944115368953: XenVbd     IRQL = 9
12944115368953: XenVbd     Completing in-flight srb 89851FB4 with status SRB_STATUS_BUS_RESET
12944115368953: XenVbd     Completing in-flight srb 89A82C04 with status SRB_STATUS_BUS_RESET
12944115368953: XenVbd     Completing in-flight srb 89A4325C with status SRB_STATUS_BUS_RESET
12944115368953: XenVbd     Completing in-flight srb 897ECAB4 with status SRB_STATUS_BUS_RESET
12944115368953: XenVbd     Completing in-flight srb 89A40194 with status SRB_STATUS_BUS_RESET
12944115368968: XenVbd     Completing in-flight srb 89859F34 with status SRB_STATUS_BUS_RESET
12944115368968: XenVbd     Completing in-flight srb 89A49FB4 with status SRB_STATUS_BUS_RESET
12944115368968: XenVbd     Completing in-flight srb 89A8CC34 with status SRB_STATUS_BUS_RESET
12944115368968: XenVbd     Completing in-flight srb 898593C4 with status SRB_STATUS_BUS_RESET
12944115368968: XenVbd <-- XenVbd_HwScsiResetBus
12944115372312: XenVbd     discarding reset shadow
12944115372312: XenVbd     discarding reset shadow
12944115372312: XenVbd     discarding reset shadow
12944115372312: XenVbd     discarding reset shadow
12944115372312: XenVbd     discarding reset shadow
12944115372328: XenVbd     discarding reset shadow
12944115372328: XenVbd     discarding reset shadow
12944115372328: XenVbd     discarding reset shadow
12944115372359: XenVbd     discarding reset shadow
12944115966062: XenVbd     WARNING: SRB completion time 10843ms
12944115966062: XenVbd     WARNING: SRB completion time 10390ms
12944115966062: XenVbd     WARNING: SRB completion time 10390ms
12944115966078: XenVbd     WARNING: SRB completion time 10187ms
12944115966093: XenVbd     WARNING: SRB completion time 10421ms
12944115966109: XenVbd     WARNING: SRB completion time 10390ms
12944115966109: XenVbd     WARNING: SRB completion time 10390ms
12944115966109: XenVbd     WARNING: SRB completion time 10171ms
12944115966109: XenVbd     WARNING: SRB completion time 10281ms
12944115966140: XenVbd     WARNING: SRB completion time 9968ms
12944116065968: XenVbd --> XenVbd_HwScsiResetBus
12944116065968: XenVbd     IRQL = 9
12944116065968: XenVbd     Completing in-flight srb 89A49FB4 with status SRB_STATUS_BUS_RESET
12944116065968: XenVbd     Completing in-flight srb 89850E1C with status SRB_STATUS_BUS_RESET
12944116065968: XenVbd     Completing in-flight srb 89A40194 with status SRB_STATUS_BUS_RESET
12944116065968: XenVbd     Completing in-flight srb 89986D1C with status SRB_STATUS_BUS_RESET
12944116065984: XenVbd     Completing in-flight srb 89A4325C with status SRB_STATUS_BUS_RESET
12944116065984: XenVbd     Completing in-flight srb 898B40B4 with status SRB_STATUS_BUS_RESET
12944116065984: XenVbd     Completing in-flight srb 89A82C04 with status SRB_STATUS_BUS_RESET
12944116065984: XenVbd     Completing in-flight srb 89859F34 with status SRB_STATUS_BUS_RESET
12944116065984: XenVbd     Completing in-flight srb 898D68F4 with status SRB_STATUS_BUS_RESET
12944116065984: XenVbd     Completing in-flight srb 89841A1C with status SRB_STATUS_BUS_RESET
12944116066000: XenVbd     Completing in-flight srb 89AE8D1C with status SRB_STATUS_BUS_RESET
12944116066000: XenVbd     Completing in-flight srb 897EBE1C with status SRB_STATUS_BUS_RESET
12944116066000: XenVbd     Completing in-flight srb 89A4375C with status SRB_STATUS_BUS_RESET
12944116066000: XenVbd     Completing in-flight srb 898E6C34 with status SRB_STATUS_BUS_RESET
12944116066000: XenVbd     Completing in-flight srb 898360B4 with status SRB_STATUS_BUS_RESET
12944116066000: XenVbd     Completing in-flight srb 898593C4 with status SRB_STATUS_BUS_RESET
12944116066000: XenVbd <-- XenVbd_HwScsiResetBus
12944116079968: XenVbd --> XenVbd_HwScsiResetBus
12944116079968: XenVbd     IRQL = 9
12944116079968: XenVbd     Completing in-flight srb 89850E1C with status SRB_STATUS_BUS_RESET
12944116079968: XenVbd     Completing in-flight srb 89986D1C with status SRB_STATUS_BUS_RESET
12944116079968: XenVbd     Completing in-flight srb 89AE8D1C with status SRB_STATUS_BUS_RESET
12944116079968: XenVbd     Completing in-flight srb 89A49FB4 with status SRB_STATUS_BUS_RESET
12944116079984: XenVbd     Completing in-flight srb 89A4375C with status SRB_STATUS_BUS_RESET
12944116079984: XenVbd     Completing in-flight srb 898593C4 with status SRB_STATUS_BUS_RESET
12944116079984: XenVbd     Completing in-flight srb 89A82C04 with status SRB_STATUS_BUS_RESET
12944116079984: XenVbd     Completing in-flight srb 89A40194 with status SRB_STATUS_BUS_RESET
12944116079984: XenVbd     Completing in-flight srb 89A4325C with status SRB_STATUS_BUS_RESET
12944116079984: XenVbd     Completing in-flight srb 898B40B4 with status SRB_STATUS_BUS_RESET
12944116080000: XenVbd     Completing in-flight srb 89841A1C with status SRB_STATUS_BUS_RESET
12944116080000: XenVbd     Completing in-flight srb 89851FB4 with status SRB_STATUS_BUS_RESET
12944116080000: XenVbd     Completing in-flight srb 897EBE1C with status SRB_STATUS_BUS_RESET
12944116080000: XenVbd     Completing in-flight srb 898E6C34 with status SRB_STATUS_BUS_RESET
12944116080000: XenVbd     Completing in-flight srb 898360B4 with status SRB_STATUS_BUS_RESET
12944116080000: XenVbd     Completing in-flight srb 898D68F4 with status SRB_STATUS_BUS_RESET
12944116080000: XenVbd <-- XenVbd_HwScsiResetBus
12944116093968: XenVbd --> XenVbd_HwScsiResetBus
12944116093968: XenVbd     IRQL = 9
12944116093968: XenVbd     completing queued SRB 89859F34 with status SRB_STATUS_BUS_RESET
12944116093968: XenVbd <-- XenVbd_HwScsiResetBus
12944116107968: XenVbd --> XenVbd_HwScsiResetBus
12944116107968: XenVbd     IRQL = 9
12944116107968: XenVbd     completing queued SRB 89986D1C with status SRB_STATUS_BUS_RESET
12944116107968: XenVbd <-- XenVbd_HwScsiResetBus
12944116114125: XenVbd     discarding reset shadow
12944116114140: XenVbd     discarding reset shadow
12944116114140: XenVbd     discarding reset shadow
12944116114140: XenVbd     discarding reset shadow
12944116114140: XenVbd     discarding reset shadow
12944116114140: XenVbd     discarding reset shadow
12944116114140: XenVbd     discarding reset shadow
12944116114140: XenVbd     discarding reset shadow
12944116114140: XenVbd     discarding reset shadow
12944116114140: XenVbd     discarding reset shadow
12944116114140: XenVbd     discarding reset shadow
12944116114250: XenVbd     discarding reset shadow
12944116114250: XenVbd     discarding reset shadow
12944116114265: XenVbd     discarding reset shadow
12944116114265: XenVbd     discarding reset shadow
12944116114265: XenVbd     discarding reset shadow
12944116114265: XenVbd     discarding reset shadow
12944116114265: XenVbd     discarding reset shadow
12944116114281: XenVbd     discarding reset shadow
12944116114281: XenVbd     discarding reset shadow
12944116114281: XenVbd     discarding reset shadow
12944116114281: XenVbd     discarding reset shadow
12944116114281: XenVbd     discarding reset shadow
12944116114281: XenVbd     discarding reset shadow
12944116114281: XenVbd     discarding reset shadow
12944116114281: XenVbd     discarding reset shadow
12944116114296: XenVbd     discarding reset shadow
12944116114296: XenVbd     discarding reset shadow
12944116114296: XenVbd     discarding reset shadow
12944116114296: XenVbd     discarding reset shadow
12944116114343: XenVbd     discarding reset shadow
12944116114359: XenVbd     discarding reset shadow
12944116563968: XenVbd --> XenVbd_HwScsiResetBus
12944116563968: XenVbd     IRQL = 9
12944116563968: XenVbd     Completing in-flight srb 89A49FB4 with status SRB_STATUS_BUS_RESET
12944116563968: XenVbd     Completing in-flight srb 89A82C04 with status SRB_STATUS_BUS_RESET
12944116563968: XenVbd     Completing in-flight srb 89A4325C with status SRB_STATUS_BUS_RESET
12944116563984: XenVbd     Completing in-flight srb 89987D9C with status SRB_STATUS_BUS_RESET
12944116563984: XenVbd     Completing in-flight srb 89841A1C with status SRB_STATUS_BUS_RESET
12944116563984: XenVbd     Completing in-flight srb 898B40B4 with status SRB_STATUS_BUS_RESET
12944116563984: XenVbd     Completing in-flight srb 89851FB4 with status SRB_STATUS_BUS_RESET
12944116563984: XenVbd     Completing in-flight srb 898593C4 with status SRB_STATUS_BUS_RESET
12944116563984: XenVbd     Completing in-flight srb 898360B4 with status SRB_STATUS_BUS_RESET
12944116564000: XenVbd     Completing in-flight srb 897EBE1C with status SRB_STATUS_BUS_RESET
12944116564000: XenVbd     Completing in-flight srb 89859F34 with status SRB_STATUS_BUS_RESET
12944116564000: XenVbd     Completing in-flight srb 89986D1C with status SRB_STATUS_BUS_RESET
12944116564000: XenVbd     Completing in-flight srb 898D68F4 with status SRB_STATUS_BUS_RESET
12944116564000: XenVbd     Completing in-flight srb 89A4375C with status SRB_STATUS_BUS_RESET
12944116564000: XenVbd <-- XenVbd_HwScsiResetBus
12944116569015: XenVbd     discarding reset shadow
12944116569015: XenVbd     discarding reset shadow
12944116569015: XenVbd     discarding reset shadow
12944116569015: XenVbd     discarding reset shadow
12944116569015: XenVbd     discarding reset shadow
12944116569015: XenVbd     discarding reset shadow
12944116569015: XenVbd     discarding reset shadow
12944116569078: XenVbd     discarding reset shadow
12944116569078: XenVbd     discarding reset shadow
12944116569093: XenVbd     discarding reset shadow
12944116569093: XenVbd     discarding reset shadow
12944116569093: XenVbd     discarding reset shadow
12944116569296: XenVbd     discarding reset shadow
12944116569296: XenVbd     discarding reset shadow
12944117834437: XenVbd     WARNING: SRB completion time 5250ms
12944117834437: XenVbd     WARNING: SRB completion time 5250ms
12944117834562: XenVbd     WARNING: SRB completion time 5093ms
12944117834562: XenVbd     WARNING: SRB completion time 5093ms
12944117834562: XenVbd     WARNING: SRB completion time 5015ms
12944119716000: XenVbd --> XenVbd_HwScsiResetBus
12944119716000: XenVbd     IRQL = 9
12944119716000: XenVbd     Completing in-flight srb 89966944 with status SRB_STATUS_BUS_RESET
12944119716000: XenVbd     Completing in-flight srb 89AE8D1C with status SRB_STATUS_BUS_RESET
12944119716015: XenVbd     Completing in-flight srb 89859F34 with status SRB_STATUS_BUS_RESET
12944119716015: XenVbd     Completing in-flight srb 89A49FB4 with status SRB_STATUS_BUS_RESET
12944119716015: XenVbd     Completing in-flight srb 89851FB4 with status SRB_STATUS_BUS_RESET
12944119716015: XenVbd     Completing in-flight srb 897EBE1C with status SRB_STATUS_BUS_RESET
12944119716031: XenVbd     Completing in-flight srb 897ECAB4 with status SRB_STATUS_BUS_RESET
12944119716031: XenVbd <-- XenVbd_HwScsiResetBus
12944119731000: XenVbd --> XenVbd_HwScsiResetBus
12944119731000: XenVbd     IRQL = 9
12944119731000: XenVbd     Completing in-flight srb 89A40194 with status SRB_STATUS_BUS_RESET
12944119731000: XenVbd     Completing in-flight srb 898E6C34 with status SRB_STATUS_BUS_RESET
12944119731000: XenVbd     Completing in-flight srb 89859F34 with status SRB_STATUS_BUS_RESET
12944119731000: XenVbd     Completing in-flight srb 89A49FB4 with status SRB_STATUS_BUS_RESET
12944119731000: XenVbd     Completing in-flight srb 897EBE1C with status SRB_STATUS_BUS_RESET
12944119731015: XenVbd     Completing in-flight srb 89966944 with status SRB_STATUS_BUS_RESET
12944119731015: XenVbd     Completing in-flight srb 89AE8D1C with status SRB_STATUS_BUS_RESET
12944119731015: XenVbd     Completing in-flight srb 89851FB4 with status SRB_STATUS_BUS_RESET
12944119731015: XenVbd     Completing in-flight srb 897ECAB4 with status SRB_STATUS_BUS_RESET
12944119731015: XenVbd <-- XenVbd_HwScsiResetBus
12944119746000: XenVbd --> XenVbd_HwScsiResetBus
12944119746000: XenVbd     IRQL = 9
12944119746000: XenVbd     Completing in-flight srb 897ECAB4 with status SRB_STATUS_BUS_RESET
12944119746000: XenVbd     Completing in-flight srb 89AE8D1C with status SRB_STATUS_BUS_RESET
12944119746000: XenVbd     Completing in-flight srb 89966944 with status SRB_STATUS_BUS_RESET
12944119746015: XenVbd     Completing in-flight srb 89851FB4 with status SRB_STATUS_BUS_RESET
12944119746015: XenVbd     Completing in-flight srb 89A40194 with status SRB_STATUS_BUS_RESET
12944119746015: XenVbd     Completing in-flight srb 898E6C34 with status SRB_STATUS_BUS_RESET
12944119746015: XenVbd     Completing in-flight srb 89A49FB4 with status SRB_STATUS_BUS_RESET
12944119746015: XenVbd     Completing in-flight srb 89859F34 with status SRB_STATUS_BUS_RESET
12944119746015: XenVbd     Completing in-flight srb 897EBE1C with status SRB_STATUS_BUS_RESET
12944119746031: XenVbd <-- XenVbd_HwScsiResetBus
12944119760000: XenVbd --> XenVbd_HwScsiResetBus
12944119760000: XenVbd     IRQL = 9
12944119760000: XenVbd     Completing in-flight srb 897ECAB4 with status SRB_STATUS_BUS_RESET
12944119760000: XenVbd     Completing in-flight srb 897EBE1C with status SRB_STATUS_BUS_RESET
12944119760000: XenVbd     Completing in-flight srb 89851FB4 with status SRB_STATUS_BUS_RESET
12944119760000: XenVbd     Completing in-flight srb 89A49FB4 with status SRB_STATUS_BUS_RESET
12944119760000: XenVbd     Completing in-flight srb 89859F34 with status SRB_STATUS_BUS_RESET
12944119760015: XenVbd     Completing in-flight srb 898E6C34 with status SRB_STATUS_BUS_RESET
12944119760015: XenVbd     Completing in-flight srb 89966944 with status SRB_STATUS_BUS_RESET
12944119760015: XenVbd <-- XenVbd_HwScsiResetBus
12944119760640: XenVbd     discarding reset shadow
12944119760640: XenVbd     discarding reset shadow
12944119760640: XenVbd     discarding reset shadow
12944119760656: XenVbd     discarding reset shadow
12944119760656: XenVbd     discarding reset shadow
12944119760656: XenVbd     discarding reset shadow
12944119760656: XenVbd     discarding reset shadow
12944119760656: XenVbd     discarding reset shadow
12944119760671: XenVbd     discarding reset shadow
12944119760671: XenVbd     discarding reset shadow
12944119760687: XenVbd     discarding reset shadow
12944119760703: XenVbd     discarding reset shadow
12944119760703: XenVbd     discarding reset shadow
12944119760703: XenVbd     discarding reset shadow
12944119760703: XenVbd     discarding reset shadow
12944119760718: XenVbd     discarding reset shadow
12944119760718: XenVbd     discarding reset shadow
12944119760718: XenVbd     discarding reset shadow
12944119760718: XenVbd     discarding reset shadow
12944119760718: XenVbd     discarding reset shadow
12944119760718: XenVbd     discarding reset shadow
12944119760718: XenVbd     discarding reset shadow
12944119760718: XenVbd     discarding reset shadow
12944119760734: XenVbd     discarding reset shadow
12944119760796: XenVbd     discarding reset shadow
12944119760796: XenVbd     discarding reset shadow
12944119760812: XenVbd     discarding reset shadow
12944119760812: XenVbd     discarding reset shadow
12944119760812: XenVbd     discarding reset shadow
12944119760812: XenVbd     discarding reset shadow
12944119760812: XenVbd     discarding reset shadow
12944119760812: XenVbd     discarding reset shadow
12944120549015: XenVbd --> XenVbd_HwScsiResetBus
12944120549015: XenVbd     IRQL = 9
12944120549015: XenVbd     Completing in-flight srb 89966944 with status SRB_STATUS_BUS_RESET
12944120549015: XenVbd     Completing in-flight srb 897ECAB4 with status SRB_STATUS_BUS_RESET
12944120549015: XenVbd     Completing in-flight srb 89AE8D1C with status SRB_STATUS_BUS_RESET
12944120549015: XenVbd     Completing in-flight srb 89851FB4 with status SRB_STATUS_BUS_RESET
12944120549031: XenVbd     Completing in-flight srb 89A49FB4 with status SRB_STATUS_BUS_RESET
12944120549031: XenVbd     Completing in-flight srb 897EBE1C with status SRB_STATUS_BUS_RESET
12944120549031: XenVbd     Completing in-flight srb 89A40194 with status SRB_STATUS_BUS_RESET
12944120549031: XenVbd     Completing in-flight srb 898E6C34 with status SRB_STATUS_BUS_RESET
12944120549046: XenVbd <-- XenVbd_HwScsiResetBus
12944120549593: XenVbd     discarding reset shadow
12944120549593: XenVbd     discarding reset shadow
12944120549609: XenVbd     discarding reset shadow
12944120549609: XenVbd     discarding reset shadow
12944120549609: XenVbd     discarding reset shadow
12944120549734: XenVbd     discarding reset shadow
12944120549750: XenVbd     discarding reset shadow
12944120549750: XenVbd     discarding reset shadow
12944120570015: XenVbd --> XenVbd_HwScsiResetBus
12944120570015: XenVbd     IRQL = 9
12944120570015: XenVbd     Completing in-flight srb 89859F34 with status SRB_STATUS_BUS_RESET
12944120570015: XenVbd     Completing in-flight srb 897ECAB4 with status SRB_STATUS_BUS_RESET
12944120570031: XenVbd     Completing in-flight srb 89AE8D1C with status SRB_STATUS_BUS_RESET
12944120570031: XenVbd     Completing in-flight srb 89A49FB4 with status SRB_STATUS_BUS_RESET
12944120570031: XenVbd     Completing in-flight srb 898E6C34 with status SRB_STATUS_BUS_RESET
12944120570031: XenVbd     Completing in-flight srb 89851FB4 with status SRB_STATUS_BUS_RESET
12944120570031: XenVbd     Completing in-flight srb 897EBE1C with status SRB_STATUS_BUS_RESET
12944120570031: XenVbd <-- XenVbd_HwScsiResetBus
12944120570343: XenVbd     discarding reset shadow
12944120570343: XenVbd     discarding reset shadow
12944120570343: XenVbd     discarding reset shadow
12944120570343: XenVbd     discarding reset shadow
12944120570500: XenVbd     discarding reset shadow
12944120570500: XenVbd     discarding reset shadow
12944120570515: XenVbd     discarding reset shadow
12944120581093: XenVbd     WARNING: SRB completion time 6437ms
12944120581109: XenVbd     WARNING: SRB completion time 6437ms
12944120581109: XenVbd     WARNING: SRB completion time 5796ms
12944120581109: XenVbd     WARNING: SRB completion time 5796ms
12944120581109: XenVbd     WARNING: SRB completion time 5796ms
12944120581109: XenVbd     WARNING: SRB completion time 5796ms
12944120581109: XenVbd     WARNING: SRB completion time 5812ms
12944120581171: XenVbd     WARNING: SRB completion time 5875ms
12944120587453: XenVbd     WARNING: SRB completion time 6234ms
12944120587453: XenVbd     WARNING: SRB completion time 6250ms
12944120587781: XenVbd     WARNING: SRB completion time 6328ms
12944120587781: XenVbd     WARNING: SRB completion time 6328ms
12944120587781: XenVbd     WARNING: SRB completion time 6296ms
12944120601875: XenVbd     WARNING: SRB completion time 10500ms
12944120601875: XenVbd     WARNING: SRB completion time 10421ms
12944120601875: XenVbd     WARNING: SRB completion time 10421ms
12944120601937: XenVbd     WARNING: SRB completion time 10484ms
12944120601937: XenVbd     WARNING: SRB completion time 10468ms
12944120601937: XenVbd     WARNING: SRB completion time 10437ms
12944120601968: XenVbd     WARNING: SRB completion time 8453ms
12944120625250: XenVbd     WARNING: SRB completion time 9156ms
12944120625250: XenVbd     WARNING: SRB completion time 9062ms
12944120625265: XenVbd     WARNING: SRB completion time 9062ms
12944120632937: XenVbd     WARNING: SRB completion time 16734ms
12944120633171: XenVbd     WARNING: SRB completion time 16968ms
12944120633171: XenVbd     WARNING: SRB completion time 16968ms
12944120633203: XenVbd     WARNING: SRB completion time 15203ms
12944120633203: XenVbd     WARNING: SRB completion time 7937ms
12944120633453: XenVbd     WARNING: SRB completion time 8187ms
12944120633453: XenVbd     WARNING: SRB completion time 8187ms
12944120651328: XenVbd     WARNING: SRB completion time 9671ms
12944120651343: XenVbd     WARNING: SRB completion time 9671ms
12944120651343: XenVbd     WARNING: SRB completion time 9671ms
12944120651343: XenVbd     WARNING: SRB completion time 9437ms
12944120651484: XenVbd     WARNING: SRB completion time 9593ms
12944120651500: XenVbd     WARNING: SRB completion time 9531ms
12944120651500: XenVbd     WARNING: SRB completion time 9531ms
12944120659875: XenVbd     WARNING: SRB completion time 6031ms
12944120659875: XenVbd     WARNING: SRB completion time 6000ms
12944120674015: XenVbd --> XenVbd_HwScsiResetBus
12944120674015: XenVbd     IRQL = 9
12944120674015: XenVbd     Completing in-flight srb 897ECAB4 with status SRB_STATUS_BUS_RESET
12944120674015: XenVbd     Completing in-flight srb 89851FB4 with status SRB_STATUS_BUS_RESET
12944120674015: XenVbd     Completing in-flight srb 897EBE1C with status SRB_STATUS_BUS_RESET
12944120674015: XenVbd     Completing in-flight srb 89966944 with status SRB_STATUS_BUS_RESET
12944120674015: XenVbd     Completing in-flight srb 89A49FB4 with status SRB_STATUS_BUS_RESET
12944120674031: XenVbd     Completing in-flight srb 89A40194 with status SRB_STATUS_BUS_RESET
12944120674031: XenVbd     Completing in-flight srb 89AE7FB4 with status SRB_STATUS_BUS_RESET
12944120674031: XenVbd     Completing in-flight srb 89AE8D1C with status SRB_STATUS_BUS_RESET
12944120674031: XenVbd     Completing in-flight srb 898E6C34 with status SRB_STATUS_BUS_RESET
12944120674031: XenVbd <-- XenVbd_HwScsiResetBus
12944120675421: XenVbd     discarding reset shadow
12944120675421: XenVbd     discarding reset shadow
12944120675437: XenVbd     discarding reset shadow
12944120675437: XenVbd     discarding reset shadow
12944120675437: XenVbd     discarding reset shadow
12944120675437: XenVbd     discarding reset shadow
12944120675500: XenVbd     discarding reset shadow
12944120675500: XenVbd     discarding reset shadow
12944120675515: XenVbd     discarding reset shadow
12944120728562: XenVbd     WARNING: SRB completion time 5015ms
12944120728562: XenVbd     WARNING: SRB completion time 5015ms
12944120780062: XenVbd     WARNING: SRB completion time 9265ms
12944120780078: XenVbd     WARNING: SRB completion time 8468ms
12944120780187: XenVbd     WARNING: SRB completion time 8593ms
12944120780187: XenVbd     WARNING: SRB completion time 8593ms
12944120780187: XenVbd     WARNING: SRB completion time 8593ms
12944122259031: XenVbd --> XenVbd_HwScsiResetBus
12944122259031: XenVbd     IRQL = 9
12944122259031: XenVbd     Completing in-flight srb 89A89704 with status SRB_STATUS_BUS_RESET
12944122259031: XenVbd     Completing in-flight srb 89964944 with status SRB_STATUS_BUS_RESET
12944122259031: XenVbd     Completing in-flight srb 89A8B884 with status SRB_STATUS_BUS_RESET
12944122259031: XenVbd     Completing in-flight srb 89A880B4 with status SRB_STATUS_BUS_RESET
12944122259046: XenVbd     Completing in-flight srb 898D1E1C with status SRB_STATUS_BUS_RESET
12944122259046: XenVbd     Completing in-flight srb 899697AC with status SRB_STATUS_BUS_RESET
12944122259046: XenVbd     Completing in-flight srb 898375D4 with status SRB_STATUS_BUS_RESET
12944122259046: XenVbd     Completing in-flight srb 898D196C with status SRB_STATUS_BUS_RESET
12944122259046: XenVbd     Completing in-flight srb 898362D4 with status SRB_STATUS_BUS_RESET
12944122259046: XenVbd     Completing in-flight srb 89A88C84 with status SRB_STATUS_BUS_RESET
12944122259062: XenVbd     Completing in-flight srb 89969C84 with status SRB_STATUS_BUS_RESET
12944122259062: XenVbd <-- XenVbd_HwScsiResetBus
12944122274031: XenVbd --> XenVbd_HwScsiResetBus
12944122274031: XenVbd     IRQL = 9
12944122274031: XenVbd     Completing in-flight srb 899697AC with status SRB_STATUS_BUS_RESET
12944122274031: XenVbd     Completing in-flight srb 898375D4 with status SRB_STATUS_BUS_RESET
12944122274031: XenVbd     Completing in-flight srb 898D1E1C with status SRB_STATUS_BUS_RESET
12944122274031: XenVbd     Completing in-flight srb 898362D4 with status SRB_STATUS_BUS_RESET
12944122274031: XenVbd     Completing in-flight srb 89969C84 with status SRB_STATUS_BUS_RESET
12944122274046: XenVbd     Completing in-flight srb 89A880B4 with status SRB_STATUS_BUS_RESET
12944122274046: XenVbd     Completing in-flight srb 89A8B884 with status SRB_STATUS_BUS_RESET
12944122274046: XenVbd     Completing in-flight srb 89A89704 with status SRB_STATUS_BUS_RESET
12944122274046: XenVbd     Completing in-flight srb 89964944 with status SRB_STATUS_BUS_RESET
12944122274046: XenVbd     Completing in-flight srb 898D196C with status SRB_STATUS_BUS_RESET
12944122274046: XenVbd     Completing in-flight srb 89A88C84 with status SRB_STATUS_BUS_RESET
12944122274062: XenVbd <-- XenVbd_HwScsiResetBus
12944122288031: XenVbd --> XenVbd_HwScsiResetBus
12944122288031: XenVbd     IRQL = 9
12944122288031: XenVbd     Completing in-flight srb 89A8B884 with status SRB_STATUS_BUS_RESET
12944122288031: XenVbd     Completing in-flight srb 898362D4 with status SRB_STATUS_BUS_RESET
12944122288031: XenVbd     Completing in-flight srb 899697AC with status SRB_STATUS_BUS_RESET
12944122288046: XenVbd     Completing in-flight srb 89A89704 with status SRB_STATUS_BUS_RESET
12944122288046: XenVbd     Completing in-flight srb 89969C84 with status SRB_STATUS_BUS_RESET
12944122288046: XenVbd     Completing in-flight srb 898D196C with status SRB_STATUS_BUS_RESET
12944122288046: XenVbd     Completing in-flight srb 898D1E1C with status SRB_STATUS_BUS_RESET
12944122288062: XenVbd     Completing in-flight srb 89964944 with status SRB_STATUS_BUS_RESET
12944122288062: XenVbd     Completing in-flight srb 89A88C84 with status SRB_STATUS_BUS_RESET
12944122288062: XenVbd     Completing in-flight srb 898375D4 with status SRB_STATUS_BUS_RESET
12944122288062: XenVbd <-- XenVbd_HwScsiResetBus
12944122302031: XenVbd --> XenVbd_HwScsiResetBus
12944122302031: XenVbd     IRQL = 9
12944122302031: XenVbd     completing queued SRB 89A880B4 with status SRB_STATUS_BUS_RESET
12944122302031: XenVbd <-- XenVbd_HwScsiResetBus
12944122316031: XenVbd --> XenVbd_HwScsiResetBus
12944122316031: XenVbd     IRQL = 9
12944122316031: XenVbd     completing queued SRB 898D1E1C with status SRB_STATUS_BUS_RESET
12944122316031: XenVbd <-- XenVbd_HwScsiResetBus
12944122327171: XenVbd --> DriverEntry
12944122327171: XenVbd     IRQL = 31
12944122327171: XenVbd     DriverObject = 00000000, RegistryPath = 00000000
12944122327171: XenVbd --> XenVbd_HwScsiFindAdapter
12944122327171: XenVbd     IRQL = 31
12944122327171: XenVbd     xvdd = 89333300
12944122327171: XenVbd     BusInterruptLevel = 28
12944122327171: XenVbd     BusInterruptVector = 01c
12944122327171: XenVbd     NumberOfAccessRanges = 1
12944122327171: XenVbd     RangeStart = 1f2df000, RangeLength = 00001000
12944122327171: XenVbd     XEN_INIT_TYPE_VECTORS
12944122327171: XenVbd     XEN_INIT_TYPE_DEVICE_STATE - 89AB29BC
12944122327171: XenVbd     XEN_INIT_TYPE_RING - ring-ref = 8993C000
12944122327171: XenVbd     XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 7
12944122327171: XenVbd     cached_use_other = 1
12944122327171: XenVbd     XEN_INIT_TYPE_READ_STRING - device-type = disk
12944122327171: XenVbd     device-type = Disk
12944122327171: XenVbd     XEN_INIT_TYPE_READ_STRING - mode = w
12944122327171: XenVbd     mode = w
12944122327171: XenVbd     XEN_INIT_TYPE_READ_STRING - sectors = 104857600
12944122327171: XenVbd     XEN_INIT_TYPE_READ_STRING - sector-size = 512
12944122327171: XenVbd     XEN_INIT_TYPE_GRANT_ENTRIES - entries = 11
12944122327171: XenVbd     qemu_hide_flags_value = 3
12944122327171: XenVbd     aligned_buffer_data = 8933557C
12944122327171: XenVbd     aligned_buffer = 89336000
12944122327171: XenVbd     ConfigInfo->MaximumTransferLength = 4096
12944122327171: XenVbd     ConfigInfo->NumberOfPhysicalBreaks = 0
12944122327171: XenVbd     ConfigInfo->CachesData was initialised to 0
12944122327171: XenVbd     Dma64BitAddresses not supported
12944122327171: XenVbd <-- XenVbd_HwScsiFindAdapter
12944122327171: XenVbd --> XenVbd_HwScsiInitialize
12944122327171: XenVbd     IRQL = 31
12944122327171: XenVbd     dump_mode = 1
12944122327171: XenVbd <-- XenVbd_HwScsiInitialize
12944122327171: XenVbd     Command = INQUIRY
12944122327171: XenVbd --> XenVbd_HwScsiResetBus
12944122327171: XenVbd     IRQL = 31
12944122327171: XenVbd <-- XenVbd_HwScsiResetBus
12944122327171: XenVbd     Command = SCSIOP_START_STOP_UNIT
12944122327171: XenVbd     Command = READ_CAPACITY
12944122327171: XenVbd <-- DriverEntry
12944122327171: XenVbd     max_dump_mode_blocks = 8
12944122327171: XenVbd     max_dump_mode_length = 4096
12944122327171: XenVbd     discarding reset shadow
12944122327171: XenVbd --> XenVbd_HwScsiResetBus
12944122327171: XenVbd     IRQL = 31
12944122327171: XenVbd     Completing in-flight srb 89333058 with status SRB_STATUS_BUS_RESET
12944122327171: XenVbd <-- XenVbd_HwScsiResetBus
12944122327171: XenPCI     Grant Entry 16382 for ISCS still in use by ISCS
12944122327171: 
*** Assertion failed: !xpdd->gnttbl_table[ref].flags
***   Source File: e:\download\win-pvdrivers.hg\xenpci\gnttbl.c, line 120

12944122327171: XenNet --> XenNet_Shutdown
12944122327171: XenNet <-- XenNet_Shutdown
XenPCI     Bug check 0x0000007E (0x80000003, 0x80878113, 0xF7939CB0, 0xF79399AC)

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel