Hi Keir, Please pull: http://xenbits.xensource.com/ext/xen-ia64-unstable.hg The tree is merged up to xen-unstable.hg cset 11923:abee5c6b930d. We were busy during the 3.0.3 freeze, so there''s a lot of stuff here. Notable improvements include switching to the Tristan''s xencomm interface for hypercalls, which solves several random hypercall failures, and incorporation of Isaku''s performance tuning patches, improving our dom0 -> domU networking up to about 2Gb/s. We also have many, many bug fixes, code cleanups and smaller optimizations. This pull will also fix the current build breakages for ia64 in the xen-unstable.hg tree. You may want to check the following cset before pulling as it does venture slightly out of ia64 specific code. This just links in a couple extra c files for the PV-on-HVM build and an ifdef''d startup hook: http://xenbits.xensource.com/ext/xen-ia64-unstable.hg?cs=7c2a5f96a192 Thanks, Alex -- Alex Williamson HP Open Source & Linux Org. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Hi Keir, Please pull: http://xenbits.xensource.com/ext/xen-ia64-unstable.hg This fixes the ia64 build and adds some additional fixes and tuning. We''re still trying to catch up with some of the changes in xen-unstable, but most of the functionality for both paravirt and fully virtualized domains is still intact. Changeset 12444:f78e499dd669 is currently merged up to xen-unstable.hg changeset 12407:f026d4091322. Thanks, Alex -- Alex Williamson HP Open Source & Linux Org. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
shobha ranganathan
2006-Nov-14 23:21 UTC
[Xen-devel] Newbie Q -- how to setup virtual IDTs ?
I am trying to port a driver that register interrupt handlers for hardware counters in processor. As the IDT is owned by Xen, when I run this in host OS I get errors. I want to know how can I setup virtual IDTs such that I program the counters. On overflow, Xen is notified about the overflow and the interrupt is passed to my driver. what files do I look ? What types of hypercalls I should use ? Thanks for all your help Shobha --------------------------------- Check out the all-new Yahoo! Mail beta - Fire up a more powerful email and get things done faster. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 14/11/06 11:21 pm, "shobha ranganathan" <shobha_ranganathan@yahoo.com> wrote:> I am trying to port a driver that register interrupt handlers for hardware > counters in processor. > > As the IDT is owned by Xen, when I run this in host OS I get errors. > > I want to know how can I setup virtual IDTs such that I program the counters. > On overflow, Xen is notified about the overflow and the interrupt is passed to > my driver. > > what files do I look ? What types of hypercalls I should use ?If you are using Linux then oprofile now has support for guests running on Xen. If you are using another OS then you will need to make use of the xenoprof hypercalls provided by Xen to register your interest in hardware counters for profiling. The Xen patches for the Linux oprofile code would be a good starting point here. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Hi Keir, Please pull: http://xenbits.xensource.com/ext/xen-ia64-unstable.hg This will add MCA support for ia64 enabling retrieval of firmware error logs by dom0, fixes for netback loaded as a module, fix a race with p2m table destruction, add xenoprof support, add /dev/mem support for running X, as well other fixes and additions that bring us up to date with xen-unstable. Thanks, Alex -- Alex Williamson HP Open Source & Linux Org. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Done. You shouldn''t need HVM_PARAM_VCPUS: the tools have already setmaxvcpus, and this number is available to your HVM builder by doing a getdomaininfo and using max_vcpu_id (plus one). HVM params are really intended for registering values that Xen has some interest in -- which is not the case for this particular parameter (since it''s redundant). It seems we need to better distinguish between arch-specific and generic definitions in the hvm subdirectory (even if it''s just with comments to indicate what is what) -- there is a lot of implicitly x86 stuff right now. Also we may end up needing a clean arch-specific component to the Python xc wrapper, although a few ifdef''s are okay for now. -- Keir On 8/12/06 8:36 pm, "Alex Williamson" <alex.williamson@hp.com> wrote:> Hi Keir, > > Please pull: > > http://xenbits.xensource.com/ext/xen-ia64-unstable.hg > > This will add MCA support for ia64 enabling retrieval of firmware error > logs by dom0, fixes for netback loaded as a module, fix a race with p2m > table destruction, add xenoprof support, add /dev/mem support for > running X, as well other fixes and additions that bring us up to date > with xen-unstable. Thanks, > > Alex_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Sat, 2006-12-09 at 13:47 +0000, Keir Fraser wrote:> Done. You shouldn''t need HVM_PARAM_VCPUS: the tools have already > setmaxvcpus, and this number is available to your HVM builder by doing a > getdomaininfo and using max_vcpu_id (plus one). HVM params are really > intended for registering values that Xen has some interest in -- which is > not the case for this particular parameter (since it''s redundant).Hi Keir, Thanks for the advice, I fixed this to use getdomaininfo in our current tree. We also have two other tiny fixes in the tree that would be nice to get in for 3.0.4. Please pull the xen-ia64-unstable tree to pick these up: http://xenbits.xensource.com/ext/xen-ia64-unstable.hg Thanks, Alex -- Alex Williamson HP Open Source & Linux Org. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel