From: Christian Limpach <chris@pin.lu>
To: Steven Hand <Steven.Hand@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: NetBSD port and a couple of remarks
Date: Wed, 28 Jan 2004 17:23:10 +0100 [thread overview]
Message-ID: <031301c3e5bb$05bfb240$070414ac@pin> (raw)
In-Reply-To: E1AlnGL-0004AC-00@wisbech.cl.cam.ac.uk
> Well not sure off hand if these problems are fixed (I had a quick scan
> through the 1.0 world but it seems like ancient history :-) I did notice
> a somewhat odd behaviour in the pinning case (dropping reference counts)
> but it's possible that I just misremember how it used to work..
I use the following patch: (against the xen-1.1 tar.gz)
diff -pru ../../xeno-1.1.bk/xen/common/domain.c xen/common/domain.c
--- ../../xeno-1.1.bk/xen/common/domain.c 2003-10-29
18:27:39.000000000 +0100
+++ xen/common/domain.c 2004-01-22 00:43:16.000000000 +0100
@@ -354,6 +378,7 @@ int final_setup_guestos(struct task_stru
net_ring_t *shared_rings;
net_vif_t *net_vif;
int i;
+ struct pfn_info *page;
if ( (p->flags & PF_CONSTRUCTED) )
return -EINVAL;
@@ -362,6 +387,9 @@ int final_setup_guestos(struct task_stru
* mem mappings - set them up.
*/
phys_l2tab = meminfo->l2_pgt_addr;
+ page = frame_table + (phys_l2tab >> PAGE_SHIFT);
+ get_page_type(page);
+ get_page_tot(page);
l2tab = map_domain_mem(phys_l2tab);
memcpy(&l2tab[DOMAIN_ENTRIES_PER_L2_PAGETABLE],
&idle_pg_table[DOMAIN_ENTRIES_PER_L2_PAGETABLE],
This will result in a $40000001 count and then after a switch to another
table and an unpin of the initial table, the count will be 0.
> Anyway: strongly recommend you move to 1.2 or 1.3-devel as there are
> a large number of improvements and bug fixes in a variety of areas. It
> also makes getting technical feedback on the list a bit easier since
> most of us are using >= 1.2.
yes, xen-1.1 was the latest version available outside of bitkeeper.
> > Finally, if someone could get me a xen-1.2 and/or xen-unstable tree out
of
> > bitkeeper, that would be much appreciated.
>
> It's all free to access, e.g. just type one of
>
> bk clone bk://xen.bkbits.net/xeno-1.2.bk
> bk clone bk://xen.bkbits.net/xeno-unstable.bk
yes, except that I don't want to deal with the bitkeeper licence and figure
out whether I'm allowed to use it or not.
christian
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next prev parent reply other threads:[~2004-01-28 16:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 20:59 NetBSD port and a couple of remarks Christian Limpach
2004-01-28 7:44 ` Kip Macy
2004-01-28 8:07 ` Ian Pratt
2004-01-28 14:54 ` Christian Limpach
2004-01-28 10:49 ` Steven Hand
2004-01-28 16:23 ` Christian Limpach [this message]
2004-01-28 16:38 ` Steven Hand
2004-01-28 16:51 ` Keir Fraser
2004-01-28 17:05 ` Kip Macy
2004-01-28 18:35 ` Christian Limpach
2004-01-28 19:03 ` Ian Pratt
2004-01-28 21:28 ` Kip Macy
2004-01-28 22:59 ` Andi Kleen
2004-01-28 23:10 ` Kip Macy
2004-01-28 23:24 ` Andi Kleen
2004-01-28 23:48 ` Kip Macy
2004-01-29 0:19 ` Larry McVoy
2004-01-29 0:31 ` Kip Macy
2004-01-29 11:14 ` John Szakmeister
2004-01-28 11:24 ` Ian Pratt
2004-01-28 17:07 ` Christian Limpach
2005-03-12 20:59 ` Thorsten Glaser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='031301c3e5bb$05bfb240$070414ac@pin' \
--to=chris@pin.lu \
--cc=Steven.Hand@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.