summaryrefslogtreecommitdiff
path: root/sys/arch/hppa
diff options
context:
space:
mode:
authorMiod Vallat <miod@cvs.openbsd.org>2009-02-04 17:22:24 +0000
committerMiod Vallat <miod@cvs.openbsd.org>2009-02-04 17:22:24 +0000
commita21aeb46e91693bf0f5d1fa311ca611931440134 (patch)
treeb272c9fbb4d8333a64981f286c3a1a3943f1f472 /sys/arch/hppa
parent3f83044b5d075e543c70f21def475bd4542108ec (diff)
On systems with split BTLB, do not bother trying to insert DBTLB entries,
as PDC will lie to us pretending it did while it didn't. ok kettenis@
Diffstat (limited to 'sys/arch/hppa')
-rw-r--r--sys/arch/hppa/hppa/machdep.c41
1 files changed, 37 insertions, 4 deletions
diff --git a/sys/arch/hppa/hppa/machdep.c b/sys/arch/hppa/hppa/machdep.c
index 2b0f98e6d54..51c1d3c09ac 100644
--- a/sys/arch/hppa/hppa/machdep.c
+++ b/sys/arch/hppa/hppa/machdep.c
@@ -1,4 +1,4 @@
-/* $OpenBSD: machdep.c,v 1.169 2009/02/04 17:19:17 miod Exp $ */
+/* $OpenBSD: machdep.c,v 1.170 2009/02/04 17:22:23 miod Exp $ */
/*
* Copyright (c) 1999-2003 Michael Shalayeff
@@ -845,16 +845,48 @@ btlb_insert(space, va, pa, lenp, prot)
{
static u_int32_t mask;
register vsize_t len;
- register int error, i;
+ register int error, i, btlb_max;
if (!pdc_btlb.min_size && !pdc_btlb.max_size)
return -(ENXIO);
+ /*
+ * On PCXS processors with split BTLB, we should theoretically
+ * insert in the IBTLB (if executable mapping requested), and
+ * into the DBTLB. The PDC documentation is very clear that
+ * slot numbers are, in order, IBTLB, then DBTLB, then combined
+ * BTLB.
+ *
+ * However it also states that ``successful completion may not mean
+ * that the entire address range specified in the call has been
+ * mapped in the block TLB. For both fixed range slots and variable
+ * range slots, complete coverage of the address range specified
+ * is not guaranteed. Only a portion of the address range specified
+ * may get mapped as a result''.
+ *
+ * On an HP 9000/720 with PDC ROM v1.2, it turns out that IBTLB
+ * entries are inserted as expected, but no DBTLB gets inserted
+ * at all, despite PDC returning success.
+ *
+ * So play it dumb, and do not attempt to insert DBTLB entries at
+ * all on split BTLB systems. Callers are supposed to be able to
+ * cope with this.
+ */
+
+ if (pdc_btlb.finfo.num_c == 0) {
+ if ((prot & TLB_EXECUTE) == 0)
+ return -(EINVAL);
+
+ btlb_max = pdc_btlb.finfo.num_i;
+ } else {
+ btlb_max = pdc_btlb.finfo.num_c;
+ }
+
/* align size */
for (len = pdc_btlb.min_size << PGSHIFT; len < *lenp; len <<= 1);
len >>= PGSHIFT;
i = ffs(~mask) - 1;
- if (len > pdc_btlb.max_size || i < 0) {
+ if (len > pdc_btlb.max_size || i < 0 || i >= btlb_max) {
#ifdef BTLBDEBUG
printf("btln_insert: too big (%u < %u < %u)\n",
pdc_btlb.min_size, len, pdc_btlb.max_size);
@@ -879,7 +911,8 @@ btlb_insert(space, va, pa, lenp, prot)
prot |= TLB_UNCACHABLE;
#ifdef BTLBDEBUG
- printf("btlb_insert(%d): %x:%x=%x[%x,%x]\n", i, space, va, pa, len, prot);
+ printf("btlb_insert(%d): %x:%x=%x[%x,%x]\n",
+ i, space, va, pa, len, prot);
#endif
if ((error = (*cpu_dbtlb_ins)(i, space, va, pa, len, prot)) < 0)
return -(EINVAL);