Skip to content

L
linux
Switch branch/tag
  1. 16 Jul, 2007 15 commits
    • David S. Miller's avatar
      [SPARC64]: Fix build regressions added by dr-cpu changes. · b14f5c10
      David S. Miller authored 
      Do not select HOTPLUG_CPU from SUN_LDOMS, that causes
HOTPLUG_CPU to be selected even on non-SMP which is
illegal.

Only build hvtramp.o when SMP, just like trampoline.o

Protect dr-cpu code in ds.c with HOTPLUG_CPU.

Likewise move ldom_startcpu_cpuid() to smp.c and protect
it and the call site with SUN_LDOMS && HOTPLUG_CPU.
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      b14f5c10
    • David S. Miller's avatar
      [SPARC64]: Unconditionally register vio_bus_type. · f8be339c
      David S. Miller authored 
      The VIO drivers register themselves unconditionally just
like those of any other bus type, so to avoid crashes
on non-VIO systems we need to always register vio_bus_type.
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      f8be339c
    • David S. Miller's avatar
      [SPARC64]: Initial LDOM cpu hotplug support. · 4f0234f4
      David S. Miller authored 
      Only adding cpus is supports at the moment, removal
will come next.

When new cpus are configured, the machine description is
updated.  When we get the configure request we pass in a
cpu mask of to-be-added cpus to the mdesc CPU node parser
so it only fetches information for those cpus.  That code
also proceeds to update the SMT/multi-core scheduling bitmaps.

cpu_up() does all the work and we return the status back
over the DS channel.

CPUs via dr-cpu need to be booted straight out of the
hypervisor, and this requires:

1) A new trampoline mechanism.  CPUs are booted straight
   out of the hypervisor with MMU disabled and running in
   physical addresses with no mappings installed in the TLB.

   The new hvtramp.S code sets up the critical cpu state,
   installs the locked TLB mappings for the kernel, and
   turns the MMU on.  It then proceeds to follow the logic
   of the existing trampoline.S SMP cpu bringup code.

2) All calls into OBP have to be disallowed when domaining
   is enabled.  Since cpus boot straight into the kernel from
   the hypervisor, OBP has no state about that cpu and therefore
   cannot handle being invoked on that cpu.

   Luckily it's only a handful of interfaces which can be called
   after the OBP device tree is obtained.  For example, rebooting,
   halting, powering-off, and setting options node variables.

CPU removal support will require some infrastructure changes
here.  Namely we'll have to process the requests via a true
kernel thread instead of in a workqueue.  workqueues run on
a per-cpu thread, but when unconfiguring we might need to
force the thread to execute on another cpu if the current cpu
is the one being removed.  Removal of a cpu also causes the kernel
to destroy that cpu's workqueue running thread.

Another issue on removal is that we may have interrupts still
pointing to the cpu-to-be-removed.  So new code will be needed
to walk the active INO list and retarget those cpus as-needed.
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      4f0234f4
    • David S. Miller's avatar
      [SPARC64]: Fix setting of variables in LDOM guest. · b3e13fbe
      David S. Miller authored 
      There is a special domain services capability for setting
variables in the OBP options node.  Guests don't have permanent
store for the OBP variables like a normal system, so they are
instead maintained in the LDOM control node or in the SC.
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      b3e13fbe
    • David S. Miller's avatar
      [SPARC64]: Fix MD property lifetime bugs. · 83292e0a
      David S. Miller authored 
      Property values cannot be referenced outside of
mdesc_grab()/mdesc_release() pairs.  The only major
offender was the VIO bus layer, easily fixed.

Add some commentary to mdesc.h describing these rules.
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      83292e0a
    • David S. Miller's avatar
      [SPARC64]: Abstract out mdesc accesses for better MD update handling. · 43fdf274
      David S. Miller authored 
      Since we have to be able to handle MD updates, having an in-tree
set of data structures representing the MD objects actually makes
things more painful.

The MD itself is easy to parse, and we can implement the existing
interfaces using direct parsing of the MD binary image.

The MD is now reference counted, so accesses have to now take the
form:

	handle = mdesc_grab();

	... operations on MD ...

	mdesc_release(handle);

The only remaining issue are cases where code holds on to references
to MD property values.  mdesc_get_property() returns a direct pointer
to the property value, most cases just pull in the information they
need and discard the pointer, but there are few that use the pointer
directly over a long lifetime.  Those will be fixed up in a subsequent
changeset.

A preliminary handler for MD update events from domain services is
there, it is rudimentry but it works and handles all of the reference
counting.  It does not check the generation number of the MDs,
and it does not generate a "add/delete" list for notification to
interesting parties about MD changes but that will be forthcoming.
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      43fdf274
    • David S. Miller's avatar
      [SPARC64]: Use more mearningful names for IRQ registry. · 133f09a1
      David S. Miller authored 
      All of the interrupts say "LDX RX" and "LDX TX" currently
which is next to useless.  Put a device specific prefix
before "RX" and "TX" instead which makes it much more
useful.
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      133f09a1
    • David S. Miller's avatar
      [SPARC64]: Initial domain-services driver. · e450992d
      David S. Miller authored 
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      e450992d
    • David S. Miller's avatar
      [SPARC64]: Export powerd facilities for external entities. · 13077d80
      David S. Miller authored 
      Besides the existing usage for power-button interrupts, we'll
want to make use of this code for domain-services where the
LDOM manager can send reboot requests to the guest node.
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      13077d80
    • David S. Miller's avatar
      [SPARC64]: Add domain-services nodes to VIO device tree. · 2c4f4ecb
      David S. Miller authored 
      They sit under the root of the MD tree unlike the rest of
the LDC channel based virtual devices.
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      2c4f4ecb
    • David S. Miller's avatar
      [SPARC64]: Assorted LDC bug cures. · cb481235
      David S. Miller authored 
      1) LDC_MODE_RELIABLE is deprecated an unused by anything, plus
   it and LDC_MODE_STREAM were mis-numbered.

2) read_stream() should try to read as much as possible into
   the per-LDC stream buffer area, so do not trim the read_nonraw()
   length by the caller's size parameter.

3) Send data ACKs when necessary in read_nonraw().

4) In read_nonraw() when we get a pure ACK, advance the RX head
   unconditionally past it.

5) Provide the ACKID field in the ldcdgb() packet dump in read_nonraw().
   This helps debugging stream mode LDC channel problems.

6) Decrease verbosity of rx_data_wait() so that it is more useful.
   A debugging message each loop iteration is too much.

7) In process_data_ack() stop the loop checking when we hit lp->tx_tail
   not lp->tx_head.

8) Set the seqid field properly in send_data_nack().
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      cb481235
    • David S. Miller's avatar
      [SPARC64]: Do not ACK an INO if it is disabled or inprogress. · 5a606b72
      David S. Miller authored 
      This is also a partial workaround for a bug in the LDOM firmware which
double-transmits RX inos during high load.  Without this, such an
event causes the kernel to loop forever in the interrupt call chain
ACK'ing but never actually running the IRQ handler (and thus clearing
the interrupt condition in the device).

There is still a bad potential effect when double INOs occur,
not covered by this changeset.  Namely, if the INO is already on
the per-cpu INO vector list, we still blindly re-insert it and
thus we can end up losing interrupts already linked in after
it.

We could deal with that by traversing the list before insertion,
but that's too expensive for this edge case.
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      5a606b72
    • David S. Miller's avatar
      [SPARC64]: Add Sun LDOM virtual disk driver. · 667ef3c3
      David S. Miller authored 
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      667ef3c3
    • David S. Miller's avatar
      [SPARC64]: Add Sun LDOM virtual network driver. · 4c521e42
      David S. Miller authored 
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      4c521e42
    • David S. Miller's avatar
      [SPARC64]: Add LDOM virtual channel driver and VIO device layer. · e53e97ce
      David S. Miller authored 
      Virtual devices on Sun Logical Domains are built on top
of a virtual channel framework.  This, with help of hypervisor
interfaces, provides a link layer protocol with basic
handshaking over which virtual device clients and servers
communicate.

Built on top of this is a VIO device protocol which has it's
own handshaking and message types.  At this layer attributes
are exchanged (disk size, network device addresses, etc.)
descriptor rings are registered, and data transfers are
triggers and replied to.
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      e53e97ce
  3. 15 Jul, 2007 25 commits
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7