Michael Roth mdr...@linux.vnet.ibm.com writes:
When CHR_EVENT_OPEN was initially added, it was CHR_EVENT_RESET, and
it was issued as a bottom-half:
86e94dea5b740dad65446c857f6959eae43e0ba6
AFAICT the only reason this was ever done in a BH was because it was
initially used to to issue a
On Thu, May 30, 2013 at 11:55:56AM -0500, Anthony Liguori wrote:
Michael Roth mdr...@linux.vnet.ibm.com writes:
When CHR_EVENT_OPEN was initially added, it was CHR_EVENT_RESET, and
it was issued as a bottom-half:
86e94dea5b740dad65446c857f6959eae43e0ba6
AFAICT the only reason this
mdroth mdr...@linux.vnet.ibm.com writes:
On Thu, May 30, 2013 at 11:55:56AM -0500, Anthony Liguori wrote:
Michael Roth mdr...@linux.vnet.ibm.com writes:
When CHR_EVENT_OPEN was initially added, it was CHR_EVENT_RESET, and
it was issued as a bottom-half:
On Thu, May 30, 2013 at 02:35:37PM -0500, Anthony Liguori wrote:
mdroth mdr...@linux.vnet.ibm.com writes:
On Thu, May 30, 2013 at 11:55:56AM -0500, Anthony Liguori wrote:
Michael Roth mdr...@linux.vnet.ibm.com writes:
When CHR_EVENT_OPEN was initially added, it was CHR_EVENT_RESET,
mdroth mdr...@linux.vnet.ibm.com writes:
On Thu, May 30, 2013 at 02:35:37PM -0500, Anthony Liguori wrote:
mdroth mdr...@linux.vnet.ibm.com writes:
On Thu, May 30, 2013 at 11:55:56AM -0500, Anthony Liguori wrote:
Michael Roth mdr...@linux.vnet.ibm.com writes:
When CHR_EVENT_OPEN was
On Thu, May 30, 2013 at 03:24:14PM -0500, Anthony Liguori wrote:
mdroth mdr...@linux.vnet.ibm.com writes:
On Thu, May 30, 2013 at 02:35:37PM -0500, Anthony Liguori wrote:
mdroth mdr...@linux.vnet.ibm.com writes:
On Thu, May 30, 2013 at 11:55:56AM -0500, Anthony Liguori wrote:
When CHR_EVENT_OPEN was initially added, it was CHR_EVENT_RESET, and
it was issued as a bottom-half:
86e94dea5b740dad65446c857f6959eae43e0ba6
AFAICT the only reason this was ever done in a BH was because it was
initially used to to issue a CHR_EVENT_RESET when we initialized the
monitor, and we