On 08/09/2011 12:23 PM, Peter Maydell wrote:
On 9 August 2011 10:02, Avi Kivity<avi@xxxxxxxxxx> wrote:
> +static const MemoryRegionOps omap_gpmc_ops = {
> + .read = omap_gpmc_read,
> + .write = omap_gpmc_write,
> + .endianness = DEVICE_NATIVE_ENDIAN,
> + .valid = {
> + .min_access_size = 4,
> + .max_access_size = 4,
> + },
> };
Does this give debug trace output for missized accesses?
Only after we implement and configure a debug policy in memory.c
That's the main point of the badread/badwrite functions...
These are broken now, aren't they?
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
