CVS log for src/sys/arch/xen/xen/pciback.c

Up to [cvs.NetBSD.org] / src / sys / arch / xen / xen

Request diff between arbitrary revisions

Keyword substitution: kv
Default branch: MAIN

in backend drivers, use xen_shm_(un)map for the rings instead of inline,
mostly duplicate code.

Add PVH support for backend drivers grant operation.
Now a domU in a PVH dom0 boots multiuser.

Mostly merge changes from HEAD upto 20200411

change xenbus_read() interface so that caller supplies the buffer and it's
size, caller doesn't free(9) the returned value any more

switch KERNFS_ALLOCENTRY() to use kmem_zalloc() instead of malloc()

Sync with HEAD

Switch NetBSD/xen to use XEN api tag RELEASE-4.11.1

The headers for this api are in sys/external/mit/xen-include-public/dist/

Sync with HEAD, resolve a few conflicts

Bifurcate the interrupt establish functions between XEN and non-XEN

Thus intr_establish_xname() becomes xen_intr_establish_xname() etc.

One consequence of this is that dom0 devices expect the native
function calls to be available and we thus provide weak aliasing for
dom0 builds to succeed. XEN and non-XEN devices are distinguished by
the PIC they are established on. XEN interrupts are exclusively
established on xen_pic, while dom0 interrupts are established on
natively available PICs.

This allows us an orthogonal path to xen device management (eg:
xenstore events) in XENPVHVM, without having to worry about unifying
the vector entry paths, etc., which is quite challenging.

Sync with HEAD, resolve a couple of conflicts

Decompose hypervisor_enable_event() into functional steps.

The hypervisor_unmask_event() step is relevant for any event.

The pirq related step is only relevant for pirq bound events.

Prune blanket usage of this, so that usage is semantically appropriate.

When using the intr_establish_xname() interface to register
XEN events, follow established x86/intr.c conventions - set
the 'legacy' irq value to -1, to indicate that the pic, pin
combination (&xen_pic, port) is used for registration.

Sync with head

Convert the last remaining users of event_set_handler() to
intr_establish_xname(,&xen_pic,...)

Sync with HEAD

similar treatment as xennetback_xenbus.c:
- protect instance list with mutex
- mark more local variables static
- mark with XXXSMP what looks suspicious
- in pciback.c use kmem_zalloc() et.al to allocate the device structures

add support for kern.intr.list aka intrctl(8) 'list' for xen

event_set_handler() and pirq_establish() now have extra intrname
parameter; shared intr_create_intrid() is used to provide the value

xen drivers were changed to pass the specific driver instance
name as the xname, e.g.  'vcpu0 clock' instead just 'clock', or
'xencons0' instead of 'xencons'

associated evcnt is now changed to use intrname - this matches native x86

update from HEAD

Sync with HEAD

2739767

file pciback.c was added on branch perseant-stdc-iso10646 on 2017-07-16 06:14:25 +0000

Remove the xen specific interrupt type for the x86 intr_handle_t
For this to work, we use the evtchn.c:get_pirq_to_evtchn() glue
function to make things easier.

Sync with HEAD

KNF. Remove extra spaces. No functional change.

Sync with HEAD

Pull up following revision(s) (requested by bouyer in ticket #1358):
	sys/arch/xen/include/xen-public/io/ring.h: revision 1.3 via patch
	sys/arch/xen/xen/pciback.c: revision 1.10 via patch
	sys/arch/xen/xen/xbdback_xenbus.c: revision 1.62 via patch
	sys/arch/xen/xen/xennetback_xenbus.c: revision 1.54 via patch
Apply patch from xsa155: make sure that the backend won't read parts of the
request again (possibly because of compiler optimisations), by using
copies and barrier.
From XSA155:
The compiler can emit optimizations in the PV backend drivers which
can lead to double fetch vulnerabilities. Specifically the shared
memory between the frontend and backend can be fetched twice (during
which time the frontend can alter the contents) possibly leading to
arbitrary code execution in backend.

Pull up following revision(s) (requested by bouyer in ticket #1358):
	sys/arch/xen/include/xen-public/io/ring.h: revision 1.3 via patch
	sys/arch/xen/xen/pciback.c: revision 1.10 via patch
	sys/arch/xen/xen/xbdback_xenbus.c: revision 1.62 via patch
	sys/arch/xen/xen/xennetback_xenbus.c: revision 1.54 via patch
Apply patch from xsa155: make sure that the backend won't read parts of the
request again (possibly because of compiler optimisations), by using
copies and barrier.
From XSA155:
The compiler can emit optimizations in the PV backend drivers which
can lead to double fetch vulnerabilities. Specifically the shared
memory between the frontend and backend can be fetched twice (during
which time the frontend can alter the contents) possibly leading to
arbitrary code execution in backend.

Pull up following revision(s) (requested by bouyer in ticket #1358):
	sys/arch/xen/include/xen-public/io/ring.h: revision 1.3 via patch
	sys/arch/xen/xen/pciback.c: revision 1.10 via patch
	sys/arch/xen/xen/xbdback_xenbus.c: revision 1.62 via patch
	sys/arch/xen/xen/xennetback_xenbus.c: revision 1.54 via patch
Apply patch from xsa155: make sure that the backend won't read parts of the
request again (possibly because of compiler optimisations), by using
copies and barrier.
From XSA155:
The compiler can emit optimizations in the PV backend drivers which
can lead to double fetch vulnerabilities. Specifically the shared
memory between the frontend and backend can be fetched twice (during
which time the frontend can alter the contents) possibly leading to
arbitrary code execution in backend.

Pull up following revision(s) (requested by bouyer in ticket #1071):
	sys/arch/xen/include/xen-public/io/ring.h: revision 1.3 via patch
	sys/arch/xen/xen/pciback.c: revision 1.10 via patch
	sys/arch/xen/xen/xbdback_xenbus.c: revision 1.62 via patch
	sys/arch/xen/xen/xennetback_xenbus.c: revision 1.54 via patch
Apply patch from xsa155: make sure that the backend won't read parts of the
request again (possibly because of compiler optimisations), by using
copies and barrier.
From XSA155:
The compiler can emit optimizations in the PV backend drivers which
can lead to double fetch vulnerabilities. Specifically the shared
memory between the frontend and backend can be fetched twice (during
which time the frontend can alter the contents) possibly leading to
arbitrary code execution in backend.

Pull up following revision(s) (requested by bouyer in ticket #1071):
	sys/arch/xen/include/xen-public/io/ring.h: revision 1.3 via patch
	sys/arch/xen/xen/pciback.c: revision 1.10 via patch
	sys/arch/xen/xen/xbdback_xenbus.c: revision 1.62 via patch
	sys/arch/xen/xen/xennetback_xenbus.c: revision 1.54 via patch
Apply patch from xsa155: make sure that the backend won't read parts of the
request again (possibly because of compiler optimisations), by using
copies and barrier.
From XSA155:
The compiler can emit optimizations in the PV backend drivers which
can lead to double fetch vulnerabilities. Specifically the shared
memory between the frontend and backend can be fetched twice (during
which time the frontend can alter the contents) possibly leading to
arbitrary code execution in backend.

Apply patch from xsa155: make sure that the backend won't read parts of the
request again (possibly because of compiler optimisations), by using
copies and barrier.
From XSA155:
The compiler can emit optimizations in the PV backend drivers which
can lead to double fetch vulnerabilities. Specifically the shared
memory between the frontend and backend can be fetched twice (during
which time the frontend can alter the contents) possibly leading to
arbitrary code execution in backend.

Rebase to HEAD as of a few days ago.

sync with head.

for a reference, the tree before this commit was tagged
as yamt-pagecache-tag8.

this commit was splitted into small chunks to avoid
a limitation of cvs.  ("Protocol error: too many arguments")

sync with head

make pci_intr_string and eisa_intr_string take a buffer and a length
instead of relying in local static storage.

correct/add protection against snprintf overflow.

sync with head

merge to -current.

Entropy-pool implementation move and cleanup.

1) Move core entropy-pool code and source/sink/sample management code
   to sys/kern from sys/dev.

2) Remove use of NRND as test for presence of entropy-pool code throughout
   source tree.

3) Remove use of RND_ENABLED in device drivers as microoptimization to
   avoid expensive operations on disabled entropy sources; make the
   rnd_add calls do this directly so all callers benefit.

4) Fix bug in recent rnd_add_data()/rnd_add_uint32() changes that might
   have lead to slight entropy overestimation for some sources.

5) Add new source types for environmental sensors, power sensors, VM
   system events, and skew between clocks, with a sample implementation
   for each.

ok releng to go in before the branch due to the difficulty of later
pullup (widespread #ifdef removal and moved files).  Tested with release
builds on amd64 and evbarm and live testing on amd64.

switch from xen3-public to xen-public.

sync to netbsd-5

sync with head

Sync with HEAD.

file pciback.c was added on branch matt-nb5-mips64 on 2010-04-21 00:33:45 +0000

Remove closes 3 & 4 from my licence. Lots of thanks to Soren Jacobsen
for the booring work !

Pull up following revision(s) (requested by bouyer in ticket #1054):
	sys/arch/xen/xen/pciback.c: revision 1.4
Move a message to debug

Pull up following revision(s) (requested by bouyer in ticket #1054):
	sys/arch/xen/xen/pciback.c: revision 1.3
Unbind the event channel after mapping the interrupt. Otherwise domain0
will share the interrupt with the domU and xen will wait for domain0 to
ack the interrupt too. Now devices that don't share an interrupt with
a device in domain0 works too.
Make sure the same PCI bus isn't published multiple times.

Pull up following revision(s) (requested by bouyer in ticket #1054):
	sys/arch/xen/xen/pciback.c: revision 1.2
- xentools also use pci vendor/product id and subsystem id; export them
via the kernfs file
- EVTCHNOP_bind_pirq wants the legacy IRQ number; so always set the
  legacy IRQ number in the PCI_INTERRUPT_REG.

Pull up following revision(s) (requested by bouyer in ticket #1054):
	sys/arch/xen/conf/files.xen: revision 1.93
	sys/arch/xen/include/pci_machdep.h: revision 1.11
	sys/arch/xen/include/xen.h: revision 1.31
	sys/arch/xen/xen/hypervisor.c: revision 1.44
	sys/arch/xen/xen/pci_intr_machdep.c: revision 1.8
	sys/arch/xen/xen/pciback.c: revision 1.1
	sys/arch/xen/xen/xen_machdep.c: revision 1.5
	sys/arch/xen/xen/xpci_xenbus.c: revision 1.1
Work in progress on PCI front-end/back-end support
front-end:
- add a xpci* at xenbus? which provides pci busses from the dom0
  xpci provides support routines for PCI config space operations and
  enumeration in xpci_xenbus.c
- hypervisor.c: do dom0-style PCI attach only ifdef DOM0OPS
- pci_intr_machdep.c:  check line value only if DOM0OPS
back-end:
- add a pciback* at pci? device which takes precedences over all
  other PCI devices (match return 500) and matches all devices passed
  to pciback.hide option on boot command line.
  It exports the PCI device informations to files in /kern/xen/pci/
- hypervisor.c: create /kern/xen earlier so pciback can create its
  entries while PCI devices are probed
- xen_machdep.c: add handling for pciback.hide=
frontend is know working on Xen 3.1.x dom0 with ahc(4) and pciide(4)
devices. uhci(4) fail when trying to allocate a large contigous DMA
buffer.
backend is work in progress; support in xentools is not there yet.

Sync with HEAD.

Commit is split, to avoid a "too many arguments" protocol error.

sync with head.

Sync with HEAD.

file pciback.c was added on branch netbsd-5 on 2009-10-03 23:54:05 +0000

file pciback.c was added on branch jym-xensuspend on 2009-05-13 17:18:50 +0000

file pciback.c was added on branch yamt-nfs-mp on 2009-05-04 08:12:14 +0000

Move a message to debug

Unbind the event channel after mapping the interrupt. Otherwise domain0
will share the interrupt with the domU and xen will wait for domain0 to
ack the interrupt too. Now devices that don't share an interrupt with
a device in domain0 works too.
Make sure the same PCI bus isn't published multiple times.

- xentools also use pci vendor/product id and subsystem id; export them
via the kernfs file
- EVTCHNOP_bind_pirq wants the legacy IRQ number; so always set the
  legacy IRQ number in the PCI_INTERRUPT_REG.

Sync with HEAD.

file pciback.c was added on branch nick-hppapmap on 2009-03-03 18:29:49 +0000

Work in progress on PCI front-end/back-end support
front-end:
- add a xpci* at xenbus? which provides pci busses from the dom0
  xpci provides support routines for PCI config space operations and
  enumeration in xpci_xenbus.c
- hypervisor.c: do dom0-style PCI attach only ifdef DOM0OPS
- pci_intr_machdep.c:  check line value only if DOM0OPS

back-end:
- add a pciback* at pci? device which takes precedences over all
  other PCI devices (match return 500) and matches all devices passed
  to pciback.hide option on boot command line.
  It exports the PCI device informations to files in /kern/xen/pci/
- hypervisor.c: create /kern/xen earlier so pciback can create its
  entries while PCI devices are probed
- xen_machdep.c: add handling for pciback.hide=

frontend is know working on Xen 3.1.x dom0 with ahc(4) and pciide(4)
devices. uhci(4) fail when trying to allocate a large contigous DMA
buffer.

backend is work in progress; support in xentools is not there yet.