> > >> MS-TFS: 157532
> >
> > > What is this line for?
> >
> > Hi Greg,
> > This line is for our internal bug repository.
> > We have an automated system to correlate bugs with fixes so that our test
> > team knows when a bug fix has been accepted upstream and they need to
> > write a new test
Hi!
Short:
1)
greg k-h> don't add marker lines like this that provide no relevancy to anyone
else.
"no relevancy to anyone else" -- strange: it "has relevance for Hyper-V
sysadmins"
For search by keywords in web archives of this mail list
1b)
greg k-h> If you want to refer to a public bug
Hi!
Short:
1)
greg k-h don't add marker lines like this that provide no relevancy to anyone
else.
no relevancy to anyone else -- strange: it has relevance for Hyper-V
sysadmins
For search by keywords in web archives of this mail list
1b)
greg k-h If you want to refer to a public bug
MS-TFS: 157532
What is this line for?
Hi Greg,
This line is for our internal bug repository.
We have an automated system to correlate bugs with fixes so that our test
team knows when a bug fix has been accepted upstream and they need to
write a new test case for it.
The
On Tue, Jun 24, 2014 at 09:44:14PM +, Dexuan Cui wrote:
> >On Tue, Jun 24, 2014 at 08:29:17AM +0800, Dexuan Cui wrote:
> >> Currently the VSC has no chance to notify the VSP of the dirty rectangle
> >> on VM
> >> panic because the notification work is done in a workqueue, and in panic()
> >>
On Tue, Jun 24, 2014 at 09:44:14PM +, Dexuan Cui wrote:
On Tue, Jun 24, 2014 at 08:29:17AM +0800, Dexuan Cui wrote:
Currently the VSC has no chance to notify the VSP of the dirty rectangle
on VM
panic because the notification work is done in a workqueue, and in panic()
the
kernel
>On Tue, Jun 24, 2014 at 08:29:17AM +0800, Dexuan Cui wrote:
>> Currently the VSC has no chance to notify the VSP of the dirty rectangle on
>> VM
>> panic because the notification work is done in a workqueue, and in panic()
>> the
>> kernel typically ends up in an infinite loop, and a typical
On Tue, Jun 24, 2014 at 08:29:17AM +0800, Dexuan Cui wrote:
> Currently the VSC has no chance to notify the VSP of the dirty rectangle on VM
> panic because the notification work is done in a workqueue, and in panic() the
> kernel typically ends up in an infinite loop, and a typical kernel config
On Tue, Jun 24, 2014 at 08:29:17AM +0800, Dexuan Cui wrote:
Currently the VSC has no chance to notify the VSP of the dirty rectangle on VM
panic because the notification work is done in a workqueue, and in panic() the
kernel typically ends up in an infinite loop, and a typical kernel config has
On Tue, Jun 24, 2014 at 08:29:17AM +0800, Dexuan Cui wrote:
Currently the VSC has no chance to notify the VSP of the dirty rectangle on
VM
panic because the notification work is done in a workqueue, and in panic()
the
kernel typically ends up in an infinite loop, and a typical kernel config
10 matches
Mail list logo
