diff options
author | Isaku Yamahata <yamahata@valinux.co.jp> | 2009-07-14 19:10:43 +0900 |
---|---|---|
committer | Anthony Liguori <aliguori@us.ibm.com> | 2009-07-16 17:28:50 -0500 |
commit | 07323531c196223293bf266bd4d3811bd24c6e34 (patch) | |
tree | a3db2b3e89b33e711b149afe123f6dc9c296081c /target-i386/svm.h | |
parent | fc7083b53008bbe5c13baab0ce869d2549bc1754 (diff) | |
download | hqemu-07323531c196223293bf266bd4d3811bd24c6e34.zip hqemu-07323531c196223293bf266bd4d3811bd24c6e34.tar.gz |
ioport: use uint{32, 16, 8}_t for ioport value and pio_addr_t for ioport address.
Using int for cpu_{in, out}[bwl] is inconsistent with other part
because for address or value, uintN_t is used by other qemu part.
At least, softmmu, CPU{Read, Write}MemoryFunc, pci, target_phys_addr_t
and the callers of cpu_{in, out}[bwl]().
This patch removes the inconsistency.
IO port has its own address space so define pio_addr_t as uint32_t
because PCI io space width is 32bit.
And use uint{32, 16, 8}_t for ioport value.
Changing signedness of value might cause subtle issue. However
only a suspicious caller is kvm_handle_io() which is ok. And other callers
pass unsigned value in the first place.
Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp>
Cc: Stuart Brady <sdbrady@ntlworld.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>
Cc: Samuel Thibault <samuel.thibault@gnu.org>
Cc: Tristan Gingold <gingold@adacore.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Diffstat (limited to 'target-i386/svm.h')
0 files changed, 0 insertions, 0 deletions