[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [PATCH 0/2] cpu_ioreq_pio, cpu_ioreq_move: simply and fix

To: qemu-devel@xxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
From: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
Date: Mon, 10 Dec 2012 18:04:21 +0000
Delivery-date: Mon, 10 Dec 2012 18:04:50 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

These two patches fix a potential infinite loop if an ioreq has a very
large count, and also simplifies the code.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

Follow-Ups:
- [Xen-devel] [PATCH 1/2] cpu_ioreq_pio, cpu_ioreq_move: introduce read_phys_req_item, write_phys_req_item
  - From: Ian Jackson
- [Xen-devel] [PATCH 2/2] cpu_ioreq_pio, cpu_ioreq_move: i should be uint32_t rather than int
  - From: Ian Jackson

Prev by Date: Re: [Xen-devel] [PATCH v2 4/8] xen/vesa: use the new fb_* functions
Next by Date: [Xen-devel] [PATCH 2/2] cpu_ioreq_pio, cpu_ioreq_move: i should be uint32_t rather than int
Previous by thread: [Xen-devel] [xen-4.1-testing test] 14662: tolerable FAIL - PUSHED
Next by thread: [Xen-devel] [PATCH 2/2] cpu_ioreq_pio, cpu_ioreq_move: i should be uint32_t rather than int
Index(es):
- Date
- Thread

Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.