From kmacy at freebsd.org Thu Aug 21 22:07:16 2008 From: kmacy at freebsd.org (Kip Macy) Date: Thu Aug 21 22:07:23 2008 Subject: the future of sun4v Message-ID: <3c1674c90808211442t707966fq29997b53a70ed2f7@mail.gmail.com> I apologise for cross-posting. I believe that there is a general expectation by freebsd users and developers that unsupported code should not be in CVS. Although sun4v is a very interesting platform for developers doing SMP work, I simply do not have the time or energy to maintain it. If someone else would like to step up and try his hand I would be supportive of his efforts. In the likely event that no one steps forward by the time that 7.1 is released I will ask that it be moved to the Attic. Thanks, Kip From kris at FreeBSD.org Fri Aug 22 11:44:30 2008 From: kris at FreeBSD.org (Kris Kennaway) Date: Fri Aug 22 11:44:47 2008 Subject: the future of sun4v In-Reply-To: <20080822113317.GD32539@server.vk2pj.dyndns.org> References: <3c1674c90808211442t707966fq29997b53a70ed2f7@mail.gmail.com> <20080822113317.GD32539@server.vk2pj.dyndns.org> Message-ID: <48AEA699.10903@FreeBSD.org> Peter Jeremy wrote: > [Replies re-directed to freebsd-sun4v] > > On 2008-Aug-21 14:42:55 -0700, Kip Macy wrote: >> I believe that there is a general expectation by freebsd users and >> developers that unsupported code should not be in CVS. Although sun4v >> is a very interesting platform for developers doing SMP work, I simply >> do not have the time or energy to maintain it. If someone else would >> like to step up and try his hand I would be supportive of his efforts. >> In the likely event that no one steps forward by the time that 7.1 is >> released I will ask that it be moved to the Attic. > > Since there are no other current SPARC CPUs that FreeBSD can run on > (the US-II has been obsolete for about 6 years and FreeBSD won't run > on any more recent sun4u chips), that will also remove the > justification for maintaining a SPARC64 port. > > I don't have the knowledge or available time to maintain the sun4v > port by myself but would be happy to be part of a team doing so. One > impediment I have is that I don't have a T-1 or T-2 system that I can > dedicate to FreeBSD. I could work on FreeBSD in a guest domain - but > since FreeBSD doesn't support either the virtual disk or virtual > network, actually getting FreeBSD running there presents somewhat of a > challenge. > There are two t1000 systems in the freebsd.org cluster that are available for people to work on. Rink Springer has also expressed interest in this. Perhaps Kip can explain some more about what things he looked at, but the most serious bugs might be in pmap or perhaps trap handling. Operationally, things like buildworld -jN die quickly with random signals, kernel traps, etc. Kris P.S. It looks like marius has made progress on US III but sun4u is still an architectural dead end. From kris at FreeBSD.org Fri Aug 22 11:44:30 2008 From: kris at FreeBSD.org (Kris Kennaway) Date: Fri Aug 22 11:44:58 2008 Subject: the future of sun4v In-Reply-To: <20080822113317.GD32539@server.vk2pj.dyndns.org> References: <3c1674c90808211442t707966fq29997b53a70ed2f7@mail.gmail.com> <20080822113317.GD32539@server.vk2pj.dyndns.org> Message-ID: <48AEA699.10903@FreeBSD.org> Peter Jeremy wrote: > [Replies re-directed to freebsd-sun4v] > > On 2008-Aug-21 14:42:55 -0700, Kip Macy wrote: >> I believe that there is a general expectation by freebsd users and >> developers that unsupported code should not be in CVS. Although sun4v >> is a very interesting platform for developers doing SMP work, I simply >> do not have the time or energy to maintain it. If someone else would >> like to step up and try his hand I would be supportive of his efforts. >> In the likely event that no one steps forward by the time that 7.1 is >> released I will ask that it be moved to the Attic. > > Since there are no other current SPARC CPUs that FreeBSD can run on > (the US-II has been obsolete for about 6 years and FreeBSD won't run > on any more recent sun4u chips), that will also remove the > justification for maintaining a SPARC64 port. > > I don't have the knowledge or available time to maintain the sun4v > port by myself but would be happy to be part of a team doing so. One > impediment I have is that I don't have a T-1 or T-2 system that I can > dedicate to FreeBSD. I could work on FreeBSD in a guest domain - but > since FreeBSD doesn't support either the virtual disk or virtual > network, actually getting FreeBSD running there presents somewhat of a > challenge. > There are two t1000 systems in the freebsd.org cluster that are available for people to work on. Rink Springer has also expressed interest in this. Perhaps Kip can explain some more about what things he looked at, but the most serious bugs might be in pmap or perhaps trap handling. Operationally, things like buildworld -jN die quickly with random signals, kernel traps, etc. Kris P.S. It looks like marius has made progress on US III but sun4u is still an architectural dead end. From nkalev at gmail.com Fri Aug 22 14:45:18 2008 From: nkalev at gmail.com (Nikolay Kalev) Date: Fri Aug 22 14:45:25 2008 Subject: sun4v arch Message-ID: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> I would also like to help as well. As KMacy knows before i asked a lot of questions for T2 types of servers but unfortunately i have no more access to those kind of hardware as well. I;m willing to participate if a team will be formated. From nkalev at gmail.com Fri Aug 22 14:46:59 2008 From: nkalev at gmail.com (Nikolay Kalev) Date: Fri Aug 22 14:47:05 2008 Subject: sun4v arch Message-ID: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> I would also like to help as well. As KMacy knows before i asked a lot of questions for T2 types of servers but unfortunately i have no more access to those kind of hardware as well. I;m willing to participate if a team will be formated. From kris at FreeBSD.org Fri Aug 22 15:04:07 2008 From: kris at FreeBSD.org (Kris Kennaway) Date: Fri Aug 22 15:04:35 2008 Subject: sun4v arch In-Reply-To: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> Message-ID: <48AED560.8010001@FreeBSD.org> Nikolay Kalev wrote: > I would also like to help as well. > As KMacy knows before i asked a lot of questions for T2 types of > servers but unfortunately i have no more access to those kind of > hardware as well. > I;m willing to participate if a team will be formated. Just so everyone is on the same page, what is needed to keep sun4v viable are people with experience with (or intention to learn about) low level architectural and implementation details of the FreeBSD kernel and the sun4v hardware platform, who know their way around things like pmap.c and other MD places where the kernel interfaces with the "bare metal", and who are willing to make a long term (multi-year) commitment to supporting the platform. Kris From kris at FreeBSD.org Fri Aug 22 15:04:07 2008 From: kris at FreeBSD.org (Kris Kennaway) Date: Fri Aug 22 15:04:35 2008 Subject: sun4v arch In-Reply-To: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> Message-ID: <48AED560.8010001@FreeBSD.org> Nikolay Kalev wrote: > I would also like to help as well. > As KMacy knows before i asked a lot of questions for T2 types of > servers but unfortunately i have no more access to those kind of > hardware as well. > I;m willing to participate if a team will be formated. Just so everyone is on the same page, what is needed to keep sun4v viable are people with experience with (or intention to learn about) low level architectural and implementation details of the FreeBSD kernel and the sun4v hardware platform, who know their way around things like pmap.c and other MD places where the kernel interfaces with the "bare metal", and who are willing to make a long term (multi-year) commitment to supporting the platform. Kris From kris at FreeBSD.org Fri Aug 22 16:57:35 2008 From: kris at FreeBSD.org (Kris Kennaway) Date: Fri Aug 22 16:57:42 2008 Subject: sun4v arch In-Reply-To: <48AEEE3C.7030006@FreeBSD.org> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> <48AEEE3C.7030006@FreeBSD.org> Message-ID: <48AEEFFA.5030804@FreeBSD.org> Pietro Cerutti wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > Kris Kennaway wrote: > | Just so everyone is on the same page, what is needed to keep sun4v > | viable are people with experience with (or intention to learn about) low > | level architectural and implementation details of the FreeBSD kernel and > | the sun4v hardware platform, who know their way around things like > | pmap.c and other MD places where the kernel interfaces with the "bare > | metal", and who are willing to make a long term (multi-year) commitment > | to supporting the platform. > > If we had docs... What documentation is unavailable? Kris From gahr at FreeBSD.org Fri Aug 22 17:07:05 2008 From: gahr at FreeBSD.org (Pietro Cerutti) Date: Fri Aug 22 17:07:37 2008 Subject: sun4v arch In-Reply-To: <48AEEFFA.5030804@FreeBSD.org> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> <48AEEE3C.7030006@FreeBSD.org> <48AEEFFA.5030804@FreeBSD.org> Message-ID: <48AEF211.4060801@FreeBSD.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Kris Kennaway wrote: | Pietro Cerutti wrote: |> -----BEGIN PGP SIGNED MESSAGE----- |> Hash: SHA512 |> |> Kris Kennaway wrote: |> | Just so everyone is on the same page, what is needed to keep sun4v |> | viable are people with experience with (or intention to learn about) |> low |> | level architectural and implementation details of the FreeBSD kernel |> and |> | the sun4v hardware platform, who know their way around things like |> | pmap.c and other MD places where the kernel interfaces with the "bare |> | metal", and who are willing to make a long term (multi-year) commitment |> | to supporting the platform. |> |> If we had docs... | | What documentation is unavailable? Low-level docs to get started diving into sys/${ARCH}/${ARCH}.. Not that easy... | | Kris - -- Pietro Cerutti gahr@FreeBSD.org PGP Public Key: http://gahr.ch/pgp -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEAREKAAYFAkiu8hAACgkQwMJqmJVx944NvACffu7Fn9S41lJxt6DEVFCYxsgm sQkAnjCh19STLdEYbbaA4y4fFxILVOnv =w0wo -----END PGP SIGNATURE----- From nkalev at gmail.com Fri Aug 22 18:21:22 2008 From: nkalev at gmail.com (Nikolay Kalev) Date: Fri Aug 22 18:21:29 2008 Subject: sun4v arch In-Reply-To: <48AEF211.4060801@FreeBSD.org> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> <48AEEE3C.7030006@FreeBSD.org> <48AEEFFA.5030804@FreeBSD.org> <48AEF211.4060801@FreeBSD.org> Message-ID: <136a340a0808221121k1715b351sdfdc149128aeca8d@mail.gmail.com> For me the problem is the hardware mostly and some documents will be realy welcome as Pietro mentioned. As for the multi-year dedication i don;t think that will be such issue. Another thing is that time will be needed to get on the right track. On Fri, Aug 22, 2008 at 8:06 PM, Pietro Cerutti wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > Kris Kennaway wrote: > | Pietro Cerutti wrote: > |> -----BEGIN PGP SIGNED MESSAGE----- > |> Hash: SHA512 > |> > |> Kris Kennaway wrote: > |> | Just so everyone is on the same page, what is needed to keep sun4v > |> | viable are people with experience with (or intention to learn about) > |> low > |> | level architectural and implementation details of the FreeBSD kernel > |> and > |> | the sun4v hardware platform, who know their way around things like > |> | pmap.c and other MD places where the kernel interfaces with the "bare > |> | metal", and who are willing to make a long term (multi-year) commitment > |> | to supporting the platform. > |> > |> If we had docs... > | > | What documentation is unavailable? > > Low-level docs to get started diving into sys/${ARCH}/${ARCH}.. > Not that easy... > > | > | Kris > > > - -- > Pietro Cerutti > gahr@FreeBSD.org > > PGP Public Key: > http://gahr.ch/pgp > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.9 (FreeBSD) > > iEYEAREKAAYFAkiu8hAACgkQwMJqmJVx944NvACffu7Fn9S41lJxt6DEVFCYxsgm > sQkAnjCh19STLdEYbbaA4y4fFxILVOnv > =w0wo > -----END PGP SIGNATURE----- > From gahr at FreeBSD.org Fri Aug 22 18:26:32 2008 From: gahr at FreeBSD.org (Pietro Cerutti) Date: Fri Aug 22 18:27:01 2008 Subject: sun4v arch In-Reply-To: <48AED560.8010001@FreeBSD.org> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> Message-ID: <48AEEE3C.7030006@FreeBSD.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Kris Kennaway wrote: | Just so everyone is on the same page, what is needed to keep sun4v | viable are people with experience with (or intention to learn about) low | level architectural and implementation details of the FreeBSD kernel and | the sun4v hardware platform, who know their way around things like | pmap.c and other MD places where the kernel interfaces with the "bare | metal", and who are willing to make a long term (multi-year) commitment | to supporting the platform. If we had docs... | Kris - -- Pietro Cerutti gahr@FreeBSD.org PGP Public Key: http://gahr.ch/pgp -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEAREKAAYFAkiu7jsACgkQwMJqmJVx946SjgCeMIDO6Q6hZSVlsfPQTJhkM3Vk BIUAmwWDU4IAqv+nyFvGRhSxblsrVh4Q =y3qu -----END PGP SIGNATURE----- From gahr at FreeBSD.org Fri Aug 22 18:26:32 2008 From: gahr at FreeBSD.org (Pietro Cerutti) Date: Fri Aug 22 18:27:12 2008 Subject: sun4v arch In-Reply-To: <48AED560.8010001@FreeBSD.org> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> Message-ID: <48AEEE3C.7030006@FreeBSD.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Kris Kennaway wrote: | Just so everyone is on the same page, what is needed to keep sun4v | viable are people with experience with (or intention to learn about) low | level architectural and implementation details of the FreeBSD kernel and | the sun4v hardware platform, who know their way around things like | pmap.c and other MD places where the kernel interfaces with the "bare | metal", and who are willing to make a long term (multi-year) commitment | to supporting the platform. If we had docs... | Kris - -- Pietro Cerutti gahr@FreeBSD.org PGP Public Key: http://gahr.ch/pgp -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEAREKAAYFAkiu7jsACgkQwMJqmJVx946SjgCeMIDO6Q6hZSVlsfPQTJhkM3Vk BIUAmwWDU4IAqv+nyFvGRhSxblsrVh4Q =y3qu -----END PGP SIGNATURE----- From xcllnt at mac.com Fri Aug 22 19:00:24 2008 From: xcllnt at mac.com (Marcel Moolenaar) Date: Fri Aug 22 19:00:42 2008 Subject: the future of sun4v In-Reply-To: <20080822113317.GD32539@server.vk2pj.dyndns.org> References: <3c1674c90808211442t707966fq29997b53a70ed2f7@mail.gmail.com> <20080822113317.GD32539@server.vk2pj.dyndns.org> Message-ID: <477C6946-2540-4122-AD66-B769A623FE01@mac.com> On Aug 22, 2008, at 4:33 AM, Peter Jeremy wrote: > [Replies re-directed to freebsd-sun4v] > > On 2008-Aug-21 14:42:55 -0700, Kip Macy wrote: >> I believe that there is a general expectation by freebsd users and >> developers that unsupported code should not be in CVS. Although sun4v >> is a very interesting platform for developers doing SMP work, I >> simply >> do not have the time or energy to maintain it. If someone else would >> like to step up and try his hand I would be supportive of his >> efforts. >> In the likely event that no one steps forward by the time that 7.1 is >> released I will ask that it be moved to the Attic. > > Since there are no other current SPARC CPUs that FreeBSD can run on > (the US-II has been obsolete for about 6 years and FreeBSD won't run > on any more recent sun4u chips), that will also remove the > justification for maintaining a SPARC64 port. Marius has been doing some great work towards US-III support. I have FreeBSD/sparc64 running on Netra SMP with US-III CPUs. While the code is not in SVN, It's in Perforce and from what I can see, it's in a very good shape. FYI, -- Marcel Moolenaar xcllnt@mac.com From xcllnt at mac.com Fri Aug 22 19:00:24 2008 From: xcllnt at mac.com (Marcel Moolenaar) Date: Fri Aug 22 19:00:42 2008 Subject: the future of sun4v In-Reply-To: <20080822113317.GD32539@server.vk2pj.dyndns.org> References: <3c1674c90808211442t707966fq29997b53a70ed2f7@mail.gmail.com> <20080822113317.GD32539@server.vk2pj.dyndns.org> Message-ID: <477C6946-2540-4122-AD66-B769A623FE01@mac.com> On Aug 22, 2008, at 4:33 AM, Peter Jeremy wrote: > [Replies re-directed to freebsd-sun4v] > > On 2008-Aug-21 14:42:55 -0700, Kip Macy wrote: >> I believe that there is a general expectation by freebsd users and >> developers that unsupported code should not be in CVS. Although sun4v >> is a very interesting platform for developers doing SMP work, I >> simply >> do not have the time or energy to maintain it. If someone else would >> like to step up and try his hand I would be supportive of his >> efforts. >> In the likely event that no one steps forward by the time that 7.1 is >> released I will ask that it be moved to the Attic. > > Since there are no other current SPARC CPUs that FreeBSD can run on > (the US-II has been obsolete for about 6 years and FreeBSD won't run > on any more recent sun4u chips), that will also remove the > justification for maintaining a SPARC64 port. Marius has been doing some great work towards US-III support. I have FreeBSD/sparc64 running on Netra SMP with US-III CPUs. While the code is not in SVN, It's in Perforce and from what I can see, it's in a very good shape. FYI, -- Marcel Moolenaar xcllnt@mac.com From peterjeremy at optushome.com.au Fri Aug 22 19:32:19 2008 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Fri Aug 22 19:32:25 2008 Subject: the future of sun4v In-Reply-To: <3c1674c90808211442t707966fq29997b53a70ed2f7@mail.gmail.com> References: <3c1674c90808211442t707966fq29997b53a70ed2f7@mail.gmail.com> Message-ID: <20080822113317.GD32539@server.vk2pj.dyndns.org> [Replies re-directed to freebsd-sun4v] On 2008-Aug-21 14:42:55 -0700, Kip Macy wrote: >I believe that there is a general expectation by freebsd users and >developers that unsupported code should not be in CVS. Although sun4v >is a very interesting platform for developers doing SMP work, I simply >do not have the time or energy to maintain it. If someone else would >like to step up and try his hand I would be supportive of his efforts. >In the likely event that no one steps forward by the time that 7.1 is >released I will ask that it be moved to the Attic. Since there are no other current SPARC CPUs that FreeBSD can run on (the US-II has been obsolete for about 6 years and FreeBSD won't run on any more recent sun4u chips), that will also remove the justification for maintaining a SPARC64 port. I don't have the knowledge or available time to maintain the sun4v port by myself but would be happy to be part of a team doing so. One impediment I have is that I don't have a T-1 or T-2 system that I can dedicate to FreeBSD. I could work on FreeBSD in a guest domain - but since FreeBSD doesn't support either the virtual disk or virtual network, actually getting FreeBSD running there presents somewhat of a challenge. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-sun4v/attachments/20080822/dfebed42/attachment.pgp From ltning at anduin.net Fri Aug 22 20:04:17 2008 From: ltning at anduin.net (=?EUC-KR?Q?Eirik_=A8=AAverby?=) Date: Fri Aug 22 20:04:24 2008 Subject: sun4v arch In-Reply-To: <136a340a0808221121k1715b351sdfdc149128aeca8d@mail.gmail.com> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> <48AEEE3C.7030006@FreeBSD.org> <48AEEFFA.5030804@FreeBSD.org> <48AEF211.4060801@FreeBSD.org> <136a340a0808221121k1715b351sdfdc149128aeca8d@mail.gmail.com> Message-ID: <860DBB8A-DDA1-4AD9-9097-BB2D215DF786@anduin.net> I have three t1000s, and could dedicate one to this effort. Would rather not move it; but give all necessary access including direct- attached x86 hw. Would that be helpful? /Eirik On 22. aug.. 2008, at 20.21, "Nikolay Kalev" wrote: > For me the problem is the hardware mostly and some documents will be > realy welcome as Pietro mentioned. > As for the multi-year dedication i don;t think that will be such > issue. Another thing is that time will be needed to get on the right > track. > > On Fri, Aug 22, 2008 at 8:06 PM, Pietro Cerutti > wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA512 >> >> Kris Kennaway wrote: >> | Pietro Cerutti wrote: >> |> -----BEGIN PGP SIGNED MESSAGE----- >> |> Hash: SHA512 >> |> >> |> Kris Kennaway wrote: >> |> | Just so everyone is on the same page, what is needed to keep >> sun4v >> |> | viable are people with experience with (or intention to learn >> about) >> |> low >> |> | level architectural and implementation details of the FreeBSD >> kernel >> |> and >> |> | the sun4v hardware platform, who know their way around things >> like >> |> | pmap.c and other MD places where the kernel interfaces with >> the "bare >> |> | metal", and who are willing to make a long term (multi-year) >> commitment >> |> | to supporting the platform. >> |> >> |> If we had docs... >> | >> | What documentation is unavailable? >> >> Low-level docs to get started diving into sys/${ARCH}/${ARCH}.. >> Not that easy... >> >> | >> | Kris >> >> >> - -- >> Pietro Cerutti >> gahr@FreeBSD.org >> >> PGP Public Key: >> http://gahr.ch/pgp >> >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v2.0.9 (FreeBSD) >> >> iEYEAREKAAYFAkiu8hAACgkQwMJqmJVx944NvACffu7Fn9S41lJxt6DEVFCYxsgm >> sQkAnjCh19STLdEYbbaA4y4fFxILVOnv >> =w0wo >> -----END PGP SIGNATURE----- >> > _______________________________________________ > freebsd-sun4v@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-sun4v > To unsubscribe, send any mail to "freebsd-sun4v-unsubscribe@freebsd.org > " > From marius at alchemy.franken.de Fri Aug 22 20:37:29 2008 From: marius at alchemy.franken.de (Marius Strobl) Date: Fri Aug 22 20:37:52 2008 Subject: the future of sun4v In-Reply-To: <48AEA699.10903@FreeBSD.org> References: <3c1674c90808211442t707966fq29997b53a70ed2f7@mail.gmail.com> <20080822113317.GD32539@server.vk2pj.dyndns.org> <48AEA699.10903@FreeBSD.org> Message-ID: <20080822201603.GA14444@alchemy.franken.de> On Fri, Aug 22, 2008 at 01:44:25PM +0200, Kris Kennaway wrote: > Peter Jeremy wrote: > >[Replies re-directed to freebsd-sun4v] > > > >On 2008-Aug-21 14:42:55 -0700, Kip Macy wrote: > >>I believe that there is a general expectation by freebsd users and > >>developers that unsupported code should not be in CVS. Although sun4v > >>is a very interesting platform for developers doing SMP work, I simply > >>do not have the time or energy to maintain it. If someone else would > >>like to step up and try his hand I would be supportive of his efforts. > >>In the likely event that no one steps forward by the time that 7.1 is > >>released I will ask that it be moved to the Attic. > > > >Since there are no other current SPARC CPUs that FreeBSD can run on > >(the US-II has been obsolete for about 6 years and FreeBSD won't run > >on any more recent sun4u chips), that will also remove the > >justification for maintaining a SPARC64 port. > > > >I don't have the knowledge or available time to maintain the sun4v > >port by myself but would be happy to be part of a team doing so. One > >impediment I have is that I don't have a T-1 or T-2 system that I can > >dedicate to FreeBSD. I could work on FreeBSD in a guest domain - but > >since FreeBSD doesn't support either the virtual disk or virtual > >network, actually getting FreeBSD running there presents somewhat of a > >challenge. > > > > There are two t1000 systems in the freebsd.org cluster that are > available for people to work on. Rink Springer has also expressed > interest in this. > > Perhaps Kip can explain some more about what things he looked at, but > the most serious bugs might be in pmap or perhaps trap handling. > Operationally, things like buildworld -jN die quickly with random > signals, kernel traps, etc. > > Kris > > P.S. It looks like marius has made progress on US III but sun4u is still > an architectural dead end. Well, let's see what architecture the upcoming Rock CPUs are; judging their feature list they appear to be a continuation of the Fujitsu sun4u line rather than a successor of UST1/2 :) Marius From marius at alchemy.franken.de Fri Aug 22 20:37:29 2008 From: marius at alchemy.franken.de (Marius Strobl) Date: Fri Aug 22 20:37:53 2008 Subject: the future of sun4v In-Reply-To: <48AEA699.10903@FreeBSD.org> References: <3c1674c90808211442t707966fq29997b53a70ed2f7@mail.gmail.com> <20080822113317.GD32539@server.vk2pj.dyndns.org> <48AEA699.10903@FreeBSD.org> Message-ID: <20080822201603.GA14444@alchemy.franken.de> On Fri, Aug 22, 2008 at 01:44:25PM +0200, Kris Kennaway wrote: > Peter Jeremy wrote: > >[Replies re-directed to freebsd-sun4v] > > > >On 2008-Aug-21 14:42:55 -0700, Kip Macy wrote: > >>I believe that there is a general expectation by freebsd users and > >>developers that unsupported code should not be in CVS. Although sun4v > >>is a very interesting platform for developers doing SMP work, I simply > >>do not have the time or energy to maintain it. If someone else would > >>like to step up and try his hand I would be supportive of his efforts. > >>In the likely event that no one steps forward by the time that 7.1 is > >>released I will ask that it be moved to the Attic. > > > >Since there are no other current SPARC CPUs that FreeBSD can run on > >(the US-II has been obsolete for about 6 years and FreeBSD won't run > >on any more recent sun4u chips), that will also remove the > >justification for maintaining a SPARC64 port. > > > >I don't have the knowledge or available time to maintain the sun4v > >port by myself but would be happy to be part of a team doing so. One > >impediment I have is that I don't have a T-1 or T-2 system that I can > >dedicate to FreeBSD. I could work on FreeBSD in a guest domain - but > >since FreeBSD doesn't support either the virtual disk or virtual > >network, actually getting FreeBSD running there presents somewhat of a > >challenge. > > > > There are two t1000 systems in the freebsd.org cluster that are > available for people to work on. Rink Springer has also expressed > interest in this. > > Perhaps Kip can explain some more about what things he looked at, but > the most serious bugs might be in pmap or perhaps trap handling. > Operationally, things like buildworld -jN die quickly with random > signals, kernel traps, etc. > > Kris > > P.S. It looks like marius has made progress on US III but sun4u is still > an architectural dead end. Well, let's see what architecture the upcoming Rock CPUs are; judging their feature list they appear to be a continuation of the Fujitsu sun4u line rather than a successor of UST1/2 :) Marius From nkalev at gmail.com Fri Aug 22 20:41:04 2008 From: nkalev at gmail.com (Nikolay Kalev) Date: Fri Aug 22 20:41:17 2008 Subject: sun4v arch In-Reply-To: <860DBB8A-DDA1-4AD9-9097-BB2D215DF786@anduin.net> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> <48AEEE3C.7030006@FreeBSD.org> <48AEEFFA.5030804@FreeBSD.org> <48AEF211.4060801@FreeBSD.org> <136a340a0808221121k1715b351sdfdc149128aeca8d@mail.gmail.com> <860DBB8A-DDA1-4AD9-9097-BB2D215DF786@anduin.net> Message-ID: <136a340a0808221341t69e6708fx2ddc97595ea94288@mail.gmail.com> On Fri, Aug 22, 2008 at 10:23 PM, Eirik ?verby wrote: > I have three t1000s, and could dedicate one to this effort. Would rather not > move it; but give all necessary access including direct-attached x86 hw. > > Would that be helpful? > yes i think it is :-) that is ok with me as soon as we can form a team > /Eirik > > On 22. aug.. 2008, at 20.21, "Nikolay Kalev" wrote: > >> For me the problem is the hardware mostly and some documents will be >> realy welcome as Pietro mentioned. >> As for the multi-year dedication i don;t think that will be such >> issue. Another thing is that time will be needed to get on the right >> track. >> >> On Fri, Aug 22, 2008 at 8:06 PM, Pietro Cerutti wrote: >>> >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA512 >>> >>> Kris Kennaway wrote: >>> | Pietro Cerutti wrote: >>> |> -----BEGIN PGP SIGNED MESSAGE----- >>> |> Hash: SHA512 >>> |> >>> |> Kris Kennaway wrote: >>> |> | Just so everyone is on the same page, what is needed to keep sun4v >>> |> | viable are people with experience with (or intention to learn about) >>> |> low >>> |> | level architectural and implementation details of the FreeBSD kernel >>> |> and >>> |> | the sun4v hardware platform, who know their way around things like >>> |> | pmap.c and other MD places where the kernel interfaces with the >>> "bare >>> |> | metal", and who are willing to make a long term (multi-year) >>> commitment >>> |> | to supporting the platform. >>> |> >>> |> If we had docs... >>> | >>> | What documentation is unavailable? >>> >>> Low-level docs to get started diving into sys/${ARCH}/${ARCH}.. >>> Not that easy... >>> >>> | >>> | Kris >>> >>> >>> - -- >>> Pietro Cerutti >>> gahr@FreeBSD.org >>> >>> PGP Public Key: >>> http://gahr.ch/pgp >>> >>> -----BEGIN PGP SIGNATURE----- >>> Version: GnuPG v2.0.9 (FreeBSD) >>> >>> iEYEAREKAAYFAkiu8hAACgkQwMJqmJVx944NvACffu7Fn9S41lJxt6DEVFCYxsgm >>> sQkAnjCh19STLdEYbbaA4y4fFxILVOnv >>> =w0wo >>> -----END PGP SIGNATURE----- >>> >> _______________________________________________ >> freebsd-sun4v@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-sun4v >> To unsubscribe, send any mail to "freebsd-sun4v-unsubscribe@freebsd.org" >> > From kmacy at freebsd.org Fri Aug 22 20:41:47 2008 From: kmacy at freebsd.org (Kip Macy) Date: Fri Aug 22 20:41:53 2008 Subject: the future of sun4v In-Reply-To: <20080822201603.GA14444@alchemy.franken.de> References: <3c1674c90808211442t707966fq29997b53a70ed2f7@mail.gmail.com> <20080822113317.GD32539@server.vk2pj.dyndns.org> <48AEA699.10903@FreeBSD.org> <20080822201603.GA14444@alchemy.franken.de> Message-ID: <3c1674c90808221341i6c97be59wcfb10979305ffdb0@mail.gmail.com> > Well, let's see what architecture the upcoming Rock CPUs are; > judging their feature list they appear to be a continuation of > the Fujitsu sun4u line rather than a successor of UST1/2 :) That is not what I've heard. -Kip From kmacy at freebsd.org Fri Aug 22 21:10:06 2008 From: kmacy at freebsd.org (Kip Macy) Date: Fri Aug 22 21:10:45 2008 Subject: the future of sun4v In-Reply-To: <20080822201603.GA14444@alchemy.franken.de> References: <3c1674c90808211442t707966fq29997b53a70ed2f7@mail.gmail.com> <20080822113317.GD32539@server.vk2pj.dyndns.org> <48AEA699.10903@FreeBSD.org> <20080822201603.GA14444@alchemy.franken.de> Message-ID: <3c1674c90808221341i6c97be59wcfb10979305ffdb0@mail.gmail.com> > Well, let's see what architecture the upcoming Rock CPUs are; > judging their feature list they appear to be a continuation of > the Fujitsu sun4u line rather than a successor of UST1/2 :) That is not what I've heard. -Kip From kris at FreeBSD.org Fri Aug 22 23:14:03 2008 From: kris at FreeBSD.org (Kris Kennaway) Date: Fri Aug 22 23:14:09 2008 Subject: sun4v arch In-Reply-To: <20080822225510.GI32539@server.vk2pj.dyndns.org> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> <20080822225510.GI32539@server.vk2pj.dyndns.org> Message-ID: <48AF4836.7000001@FreeBSD.org> Peter Jeremy wrote: > On 2008-Aug-22 17:04:00 +0200, Kris Kennaway wrote: >> Just so everyone is on the same page, what is needed to keep sun4v >> viable are people with experience with (or intention to learn about) low >> level architectural and implementation details of the FreeBSD kernel > > What documentation is currently accurate for this beyond the source > code? The only things I can quickly find are: "Design & Implementation > of FreeBSD 5.2" and "FreeBSD Architecture Handbook". The former is > getting quite old and I'm not sure how up-to-date the latter is kept. I'm not aware of any detailed documentation about how to port FreeBSD to new architectures, which is basically the skillset needed. On the other hand I'm not the best person to ask since I don't have this skillset myself. >> the sun4v hardware platform, > > Is the documentation at http://www.opensparc.net/opensparc-t1/index.html > and http://www.opensparc.net/opensparc-t2/index.html adequate for this > or is there additional information that is needed? Is there any tutorial > style documentation on the low-level T1/T2 details? > >> who know their way around things like >> pmap.c and other MD places where the kernel interfaces with the "bare >> metal", > > I've poked around the low-level details of FreeBSD/i386 and /Alpha in > the past, though I'm nothing like an expert at it. sun4v/sun4v is > only about twice the size of a 6th Edition kernel... > >> and who are willing to make a long term (multi-year) commitment >> to supporting the platform. > > Yes. > > Is there a summary of the open issues somewhere? There are no sun4v > PRs open. Basically it doesn't even get that far. As I mentioned elsewhere, buildworld -j will usually fail. Kris > http://wiki.freebsd.org/FreeBSD/sun4v effectively hasn't > been touched since November 2006 and suggests that the only critical > issue is lack of serial port support. From imp at bsdimp.com Sat Aug 23 06:53:16 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Sat Aug 23 06:53:45 2008 Subject: sun4v arch In-Reply-To: <48AEEE3C.7030006@FreeBSD.org> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> <48AEEE3C.7030006@FreeBSD.org> Message-ID: <20080823.005200.-335188553.imp@bsdimp.com> In message: <48AEEE3C.7030006@FreeBSD.org> Pietro Cerutti writes: : -----BEGIN PGP SIGNED MESSAGE----- : Hash: SHA512 : : Kris Kennaway wrote: : | Just so everyone is on the same page, what is needed to keep sun4v : | viable are people with experience with (or intention to learn about) low : | level architectural and implementation details of the FreeBSD kernel and : | the sun4v hardware platform, who know their way around things like : | pmap.c and other MD places where the kernel interfaces with the "bare : | metal", and who are willing to make a long term (multi-year) commitment : | to supporting the platform. : : If we had docs... There's a bunch of sun4v docs available. See http://www.sun.com/processors/documentation.html for example. Warner From imp at bsdimp.com Sat Aug 23 06:53:16 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Sat Aug 23 06:53:46 2008 Subject: sun4v arch In-Reply-To: <48AEEE3C.7030006@FreeBSD.org> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> <48AEEE3C.7030006@FreeBSD.org> Message-ID: <20080823.005200.-335188553.imp@bsdimp.com> In message: <48AEEE3C.7030006@FreeBSD.org> Pietro Cerutti writes: : -----BEGIN PGP SIGNED MESSAGE----- : Hash: SHA512 : : Kris Kennaway wrote: : | Just so everyone is on the same page, what is needed to keep sun4v : | viable are people with experience with (or intention to learn about) low : | level architectural and implementation details of the FreeBSD kernel and : | the sun4v hardware platform, who know their way around things like : | pmap.c and other MD places where the kernel interfaces with the "bare : | metal", and who are willing to make a long term (multi-year) commitment : | to supporting the platform. : : If we had docs... There's a bunch of sun4v docs available. See http://www.sun.com/processors/documentation.html for example. Warner From peterjeremy at optushome.com.au Sat Aug 23 11:21:22 2008 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Sat Aug 23 11:21:29 2008 Subject: sun4v arch In-Reply-To: <48AED560.8010001@FreeBSD.org> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> Message-ID: <20080822225510.GI32539@server.vk2pj.dyndns.org> On 2008-Aug-22 17:04:00 +0200, Kris Kennaway wrote: >Just so everyone is on the same page, what is needed to keep sun4v >viable are people with experience with (or intention to learn about) low >level architectural and implementation details of the FreeBSD kernel What documentation is currently accurate for this beyond the source code? The only things I can quickly find are: "Design & Implementation of FreeBSD 5.2" and "FreeBSD Architecture Handbook". The former is getting quite old and I'm not sure how up-to-date the latter is kept. >the sun4v hardware platform, Is the documentation at http://www.opensparc.net/opensparc-t1/index.html and http://www.opensparc.net/opensparc-t2/index.html adequate for this or is there additional information that is needed? Is there any tutorial style documentation on the low-level T1/T2 details? > who know their way around things like >pmap.c and other MD places where the kernel interfaces with the "bare >metal", I've poked around the low-level details of FreeBSD/i386 and /Alpha in the past, though I'm nothing like an expert at it. sun4v/sun4v is only about twice the size of a 6th Edition kernel... > and who are willing to make a long term (multi-year) commitment >to supporting the platform. Yes. Is there a summary of the open issues somewhere? There are no sun4v PRs open. http://wiki.freebsd.org/FreeBSD/sun4v effectively hasn't been touched since November 2006 and suggests that the only critical issue is lack of serial port support. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-sun4v/attachments/20080823/b37c4801/attachment.pgp From sobomax at FreeBSD.org Sun Aug 24 02:08:44 2008 From: sobomax at FreeBSD.org (Maxim Sobolev) Date: Sun Aug 24 02:09:11 2008 Subject: sun4v arch In-Reply-To: <20080822225510.GI32539@server.vk2pj.dyndns.org> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> <20080822225510.GI32539@server.vk2pj.dyndns.org> Message-ID: <48B0BEC7.1070806@FreeBSD.org> Peter Jeremy wrote: > Is there a summary of the open issues somewhere? There are no sun4v > PRs open. http://wiki.freebsd.org/FreeBSD/sun4v effectively hasn't > been touched since November 2006 and suggests that the only critical > issue is lack of serial port support. There is a better interpretation, which is that the only critical issue is lack of real users for this port, not lack of serial port support :). -Maxim From linimon at lonesome.com Sun Aug 24 04:00:42 2008 From: linimon at lonesome.com (Mark Linimon) Date: Sun Aug 24 04:00:55 2008 Subject: sun4v arch In-Reply-To: <48B0BEC7.1070806@FreeBSD.org> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> <20080822225510.GI32539@server.vk2pj.dyndns.org> <48B0BEC7.1070806@FreeBSD.org> Message-ID: <20080824034055.GB12515@soaustin.net> On Sat, Aug 23, 2008 at 06:52:07PM -0700, Maxim Sobolev wrote: > There is a better interpretation, which is that the only critical issue > is lack of real users for this port, not lack of serial port support :). My understanding is the the port is in a pre-alpha state due to unfinished work in the kernel, so expecting there to be any userbase is premature. All of our 'new' architectures which are in this state have so few non- developer users that there is hardly any reason to submit PRs. AFAICT the active developers already know what's missing :-) Our implementation of GNATS barely serves us as a problem report system; it fails almost completely as a system for listing missing features. We would need to have something like that to track the status of the non- Tier-1 ports. (I used to maintain a table of how feature-complete the various ports are, but it is now way out of date.) mcl From yanefbsd at gmail.com Sun Aug 24 04:02:09 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Sun Aug 24 04:02:15 2008 Subject: sun4v arch In-Reply-To: <48B0BEC7.1070806@FreeBSD.org> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> <20080822225510.GI32539@server.vk2pj.dyndns.org> <48B0BEC7.1070806@FreeBSD.org> Message-ID: <7d6fde3d0808232039i78fadb9bu7373e1c36f4f37a1@mail.gmail.com> On Sat, Aug 23, 2008 at 6:52 PM, Maxim Sobolev wrote: > Peter Jeremy wrote: >> >> Is there a summary of the open issues somewhere? There are no sun4v >> PRs open. http://wiki.freebsd.org/FreeBSD/sun4v effectively hasn't >> been touched since November 2006 and suggests that the only critical >> issue is lack of serial port support. > > There is a better interpretation, which is that the only critical issue is > lack of real users for this port, not lack of serial port support :). > > -Maxim Maybe some time should be spent looking at stuff from NetBSD to see whether or not they've solved some already critical porting pieces that FreeBSD lacks in this architecture? -Garrett From peterjeremy at optushome.com.au Sun Aug 24 04:23:43 2008 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Sun Aug 24 04:24:06 2008 Subject: sun4v arch In-Reply-To: <20080824034055.GB12515@soaustin.net> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> <20080822225510.GI32539@server.vk2pj.dyndns.org> <48B0BEC7.1070806@FreeBSD.org> <7d6fde3d0808232039i78fadb9bu7373e1c36f4f37a1@mail.gmail.com> Message-ID: <20080824042339.GM32539@server.vk2pj.dyndns.org> On 2008-Aug-23 22:40:55 -0500, Mark Linimon wrote: >My understanding is the the port is in a pre-alpha state due to unfinished >work in the kernel, so expecting there to be any userbase is premature. Except that the wiki gives a far more optimistic picture. >All of our 'new' architectures which are in this state have so few non- >developer users that there is hardly any reason to submit PRs. AFAICT >the active developers already know what's missing :-) That makes it very difficult for someone outside that group to come up to speed. I can't find anything in the freebsd-sun4v archvies. I was hoping that there would be a list somewhere of what state various subsystems were in and what remained to be done. wiki.freebsd.org sounds like the ideal place for this. On 2008-Aug-23 20:39:29 -0700, Garrett Cooper wrote: >Maybe some time should be spent looking at stuff from NetBSD to see >whether or not they've solved some already critical porting pieces >that FreeBSD lacks in this architecture? I can't find anything that suggests NetBSD runs on sun4v. Their sparc64 port only covers the US-I/II families and there's no mention of sun4v. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-sun4v/attachments/20080824/5c8c3739/attachment.pgp From kmacy at freebsd.org Sun Aug 24 04:39:36 2008 From: kmacy at freebsd.org (Kip Macy) Date: Sun Aug 24 04:39:59 2008 Subject: sun4v arch In-Reply-To: <20080824042339.GM32539@server.vk2pj.dyndns.org> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> <20080822225510.GI32539@server.vk2pj.dyndns.org> <48B0BEC7.1070806@FreeBSD.org> <7d6fde3d0808232039i78fadb9bu7373e1c36f4f37a1@mail.gmail.com> <20080824034055.GB12515@soaustin.net> <20080824042339.GM32539@server.vk2pj.dyndns.org> Message-ID: <3c1674c90808232139k76f8091bw34aa0f9b71437023@mail.gmail.com> Hi Peter, There really isn't any magic to bringing up a port. You compile it, install it, and then run it until it breaks. Once it breaks you spend a lot of time instrumenting the code to track down what went wrong. Then, depending on the amount of technical insight you have in to the issue, you go through a number of iterations until it is fixed. Fixing the pmap issue is "just" (notice the quotes) a matter of tracking down the missing TLB shootdowns. For anyone who chooses pick this up it will be very educational. It will also be very time consuming. -Kip On Sat, Aug 23, 2008 at 9:23 PM, Peter Jeremy wrote: > On 2008-Aug-23 22:40:55 -0500, Mark Linimon wrote: >>My understanding is the the port is in a pre-alpha state due to unfinished >>work in the kernel, so expecting there to be any userbase is premature. > > Except that the wiki gives a far more optimistic picture. > >>All of our 'new' architectures which are in this state have so few non- >>developer users that there is hardly any reason to submit PRs. AFAICT >>the active developers already know what's missing :-) > > That makes it very difficult for someone outside that group to come up > to speed. I can't find anything in the freebsd-sun4v archvies. I was > hoping that there would be a list somewhere of what state various > subsystems were in and what remained to be done. wiki.freebsd.org > sounds like the ideal place for this. > > On 2008-Aug-23 20:39:29 -0700, Garrett Cooper wrote: >>Maybe some time should be spent looking at stuff from NetBSD to see >>whether or not they've solved some already critical porting pieces >>that FreeBSD lacks in this architecture? > > I can't find anything that suggests NetBSD runs on sun4v. Their sparc64 > port only covers the US-I/II families and there's no mention of sun4v. > > -- > Peter Jeremy > Please excuse any delays as the result of my ISP's inability to implement > an MTA that is either RFC2821-compliant or matches their claimed behaviour. > From venture37 at hotmail.com Sun Aug 24 04:46:00 2008 From: venture37 at hotmail.com (Sevan / Venture37) Date: Sun Aug 24 04:46:06 2008 Subject: sun4v arch In-Reply-To: <20080824042339.GM32539@server.vk2pj.dyndns.org> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> <20080822225510.GI32539@server.vk2pj.dyndns.org> <48B0BEC7.1070806@FreeBSD.org> <7d6fde3d0808232039i78fadb9bu7373e1c36f4f37a1@mail.gmail.com> <20080824042339.GM32539@server.vk2pj.dyndns.org> Message-ID: > I can't find anything that suggests NetBSD runs on sun4v. Their sparc64 > port only covers the US-I/II families and there's no mention of sun4v. OpenBSD/sparc64 supports the sun4v architecture & has done for a while. _________________________________________________________________ Win New York holidays with Kellogg?s & Live Search http://clk.atdmt.com/UKM/go/107571440/direct/01/ From kmacy at freebsd.org Sun Aug 24 04:49:49 2008 From: kmacy at freebsd.org (Kip Macy) Date: Sun Aug 24 04:50:02 2008 Subject: sun4v arch In-Reply-To: References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> <20080822225510.GI32539@server.vk2pj.dyndns.org> <48B0BEC7.1070806@FreeBSD.org> <7d6fde3d0808232039i78fadb9bu7373e1c36f4f37a1@mail.gmail.com> <20080824042339.GM32539@server.vk2pj.dyndns.org> Message-ID: <3c1674c90808232149t58993f49x9bbc4ac561b40e4@mail.gmail.com> On Sat, Aug 23, 2008 at 9:34 PM, Sevan / Venture37 wrote: > > >> I can't find anything that suggests NetBSD runs on sun4v. Their sparc64 >> port only covers the US-I/II families and there's no mention of sun4v. > > OpenBSD/sparc64 supports the sun4v architecture & has done for a while. > Heh. The bugs that FreeBSD exhibits on sun4v won't be hit on UP and are much less prevalent without preemption. -Kip From brad at comstyle.com Sun Aug 24 06:47:08 2008 From: brad at comstyle.com (Brad) Date: Sun Aug 24 06:47:27 2008 Subject: sun4v arch Message-ID: <20080824064655.GB11196@booyah.home.comstyle.com> > I can't find anything that suggests NetBSD runs on sun4v. Their sparc64 > port only covers the US-I/II families and there's no mention of sun4v. OpenBSD/sparc64 runs UltraSPARC-T1 and UltraSPARC-T2 systems... and the com port works too. ;) In addition to UltraSPARC III, III+, IIIi, IV and Fujitsu SPARC64 V, VI, VII systems (PRIMEPOWER / Mx000). console is /virtual-devices@100/console@1 Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2008 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 4.4-current (GENERIC.MP) #7: Sun Aug 24 00:01:05 MDT 2008 root@sun4v.openbsd.org:/usr/src/sys/arch/sparc64/compile/GENERIC.MP real mem = 34225520640 (32640MB) avail mem = 33572167680 (32016MB) mainbus0 at root: SPARC Enterprise T5120 cpu0 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu1 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu2 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu3 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu4 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu5 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu6 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu7 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu8 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu9 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu10 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu11 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu12 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu13 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu14 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu15 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu16 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu17 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu18 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu19 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu20 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu21 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu22 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu23 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu24 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu25 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu26 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu27 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu28 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu29 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu30 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu31 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu32 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu33 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu34 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu35 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu36 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu37 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu38 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu39 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu40 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu41 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu42 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu43 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu44 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu45 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu46 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu47 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu48 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu49 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu50 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu51 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu52 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu53 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu54 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu55 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu56 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu57 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu58 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu59 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu60 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu61 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu62 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu63 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz vbus0 at mainbus0 "flashprom" at vbus0 not configured "channel-devices" at vbus0 not configured "n2cp" at vbus0 not configured "ncp" at vbus0 not configured "random-number-generator" at vbus0 not configured vcons0 at vbus0 vrtc0 at vbus0 "niu" at mainbus0 not configured vpci0 at mainbus0: bus 2 to 18, dvma map 80000000-ffffffff pci0 at vpci0 ppb0 at pci0 dev 0 function 0 "PLX PEX 8533" rev 0xaa pci1 at ppb0 bus 3 ppb1 at pci1 dev 1 function 0 "PLX PEX 8533" rev 0xaa pci2 at ppb1 bus 4 ppb2 at pci2 dev 0 function 0 "PLX PEX 8517" rev 0xad pci3 at ppb2 bus 5 ppb3 at pci3 dev 1 function 0 "PLX PEX 8517" rev 0xad pci4 at ppb3 bus 6 ppb4 at pci4 dev 0 function 0 "PLX PEX 8112" rev 0xaa pci5 at ppb4 bus 7 ohci0 at pci5 dev 0 function 0 "NEC USB" rev 0x43: ivec 0x16, version 1.0 ohci1 at pci5 dev 0 function 1 "NEC USB" rev 0x43: ivec 0x17, version 1.0 ehci0 at pci5 dev 0 function 2 "NEC USB" rev 0x04: ivec 0x14 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 "NEC EHCI root hub" rev 2.00/1.00 addr 1 usb1 at ohci0: USB revision 1.0 uhub1 at usb1 "NEC OHCI root hub" rev 1.00/1.00 addr 1 usb2 at ohci1: USB revision 1.0 uhub2 at usb2 "NEC OHCI root hub" rev 1.00/1.00 addr 1 ppb5 at pci3 dev 2 function 0 "PLX PEX 8517" rev 0xad pci6 at ppb5 bus 8 em0 at pci6 dev 0 function 0 "Intel PRO/1000 PT (82571EB)" rev 0x06: ivec 0x17, address 00:14:4f:d4:d2:c6 em1 at pci6 dev 0 function 1 "Intel PRO/1000 PT (82571EB)" rev 0x06: ivec 0x14, address 00:14:4f:d4:d2:c7 ppb6 at pci3 dev 3 function 0 "PLX PEX 8517" rev 0xad pci7 at ppb6 bus 9 em2 at pci7 dev 0 function 0 "Intel PRO/1000 PT (82571EB)" rev 0x06: ivec 0x14, address 00:14:4f:d4:d2:c8 em3 at pci7 dev 0 function 1 "Intel PRO/1000 PT (82571EB)" rev 0x06: ivec 0x15, address 00:14:4f:d4:d2:c9 ppb7 at pci1 dev 2 function 0 "PLX PEX 8533" rev 0xaa pci8 at ppb7 bus 10 mpi0 at pci8 dev 0 function 0 "Symbios Logic SAS1068E" rev 0x02: ivec 0x16 scsibus0 at mpi0: 112 targets, initiator 112 sd0 at scsibus0 targ 0 lun 0: SCSI3 0/direct fixed sd0: 140009MB, 14089 cyl, 24 head, 848 sec, 512 bytes/sec, 286739329 sec total sd1 at scsibus0 targ 1 lun 0: SCSI3 0/direct fixed sd1: 140009MB, 14089 cyl, 24 head, 848 sec, 512 bytes/sec, 286739329 sec total ppb8 at pci1 dev 8 function 0 "PLX PEX 8533" rev 0xaa pci9 at ppb8 bus 11 ppb9 at pci9 dev 0 function 0 "PLX PEX 8533" rev 0xaa pci10 at ppb9 bus 12 ppb10 at pci10 dev 1 function 0 "PLX PEX 8533" rev 0xaa: ivec 0x16 pci11 at ppb10 bus 13 ppb11 at pci10 dev 2 function 0 "PLX PEX 8533" rev 0xaa: ivec 0x14 pci12 at ppb11 bus 14 ppb12 at pci10 dev 8 function 0 "PLX PEX 8533" rev 0xaa: ivec 0x14 pci13 at ppb12 bus 15 ppb13 at pci10 dev 9 function 0 "PLX PEX 8533" rev 0xaa: ivec 0x16 pci14 at ppb13 bus 16 ppb14 at pci10 dev 10 function 0 "PLX PEX 8533" rev 0xaa: ivec 0x14 pci15 at ppb14 bus 17 ppb15 at pci1 dev 9 function 0 "PLX PEX 8533" rev 0xaa: ivec 0x16 pci16 at ppb15 bus 18 "pci-performance-counters" at mainbus0 not configured ebus0 at mainbus0 com0 at ebus0 addr ca0000-ca0007 ivec 0x13: ns16550a, 16 byte fifo umass0 at uhub0 port 2 configuration 1 interface 0 "Texas Instruments Incorporated 6250 FW: 03.05.02.22.562AD423" rev 2.00/2.00 addr 2 umass0: using SCSI over Bulk-Only scsibus1 at umass0: 2 targets, initiator 0 cd0 at scsibus1 targ 1 lun 0: SCSI0 5/cdrom removable uhub3 at uhub0 port 4 "Cypress Semiconductor USB2 Hub" rev 2.00/0.0b addr 3 softraid0 at root bootpath: /pci@0,0/pci@0,0/pci@2,0/scsi@0,0/disk@0,0 root on sd0a swap on sd0b dump on sd0b -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From mat.macy at gmail.com Sun Aug 24 06:48:43 2008 From: mat.macy at gmail.com (Matthew Macy) Date: Sun Aug 24 06:48:50 2008 Subject: sun4v arch In-Reply-To: <20080824064655.GB11196@booyah.home.comstyle.com> References: <20080824064655.GB11196@booyah.home.comstyle.com> Message-ID: <3c1674c90808232348v5f423e31i31c25c8c226291e7@mail.gmail.com> How much faster is a make -j32 than a make -j1? -Kip On Sat, Aug 23, 2008 at 11:46 PM, Brad wrote: >> I can't find anything that suggests NetBSD runs on sun4v. Their sparc64 >> port only covers the US-I/II families and there's no mention of sun4v. > > OpenBSD/sparc64 runs UltraSPARC-T1 and UltraSPARC-T2 systems... and the > com port works too. ;) > > In addition to UltraSPARC III, III+, IIIi, IV and Fujitsu SPARC64 V, VI, VII > systems (PRIMEPOWER / Mx000). > > > console is /virtual-devices@100/console@1 > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > Copyright (c) 1995-2008 OpenBSD. All rights reserved. http://www.OpenBSD.org > > OpenBSD 4.4-current (GENERIC.MP) #7: Sun Aug 24 00:01:05 MDT 2008 > root@sun4v.openbsd.org:/usr/src/sys/arch/sparc64/compile/GENERIC.MP > real mem = 34225520640 (32640MB) > avail mem = 33572167680 (32016MB) > mainbus0 at root: SPARC Enterprise T5120 > cpu0 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu1 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu2 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu3 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu4 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu5 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu6 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu7 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu8 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu9 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu10 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu11 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu12 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu13 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu14 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu15 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu16 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu17 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu18 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu19 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu20 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu21 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu22 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu23 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu24 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu25 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu26 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu27 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu28 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu29 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu30 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu31 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu32 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu33 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu34 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu35 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu36 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu37 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu38 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu39 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu40 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu41 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu42 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu43 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu44 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu45 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu46 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu47 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu48 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu49 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu50 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu51 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu52 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu53 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu54 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu55 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu56 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu57 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu58 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu59 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu60 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu61 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu62 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > cpu63 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz > vbus0 at mainbus0 > "flashprom" at vbus0 not configured > "channel-devices" at vbus0 not configured > "n2cp" at vbus0 not configured > "ncp" at vbus0 not configured > "random-number-generator" at vbus0 not configured > vcons0 at vbus0 > vrtc0 at vbus0 > "niu" at mainbus0 not configured > vpci0 at mainbus0: bus 2 to 18, dvma map 80000000-ffffffff > pci0 at vpci0 > ppb0 at pci0 dev 0 function 0 "PLX PEX 8533" rev 0xaa > pci1 at ppb0 bus 3 > ppb1 at pci1 dev 1 function 0 "PLX PEX 8533" rev 0xaa > pci2 at ppb1 bus 4 > ppb2 at pci2 dev 0 function 0 "PLX PEX 8517" rev 0xad > pci3 at ppb2 bus 5 > ppb3 at pci3 dev 1 function 0 "PLX PEX 8517" rev 0xad > pci4 at ppb3 bus 6 > ppb4 at pci4 dev 0 function 0 "PLX PEX 8112" rev 0xaa > pci5 at ppb4 bus 7 > ohci0 at pci5 dev 0 function 0 "NEC USB" rev 0x43: ivec 0x16, version 1.0 > ohci1 at pci5 dev 0 function 1 "NEC USB" rev 0x43: ivec 0x17, version 1.0 > ehci0 at pci5 dev 0 function 2 "NEC USB" rev 0x04: ivec 0x14 > usb0 at ehci0: USB revision 2.0 > uhub0 at usb0 "NEC EHCI root hub" rev 2.00/1.00 addr 1 > usb1 at ohci0: USB revision 1.0 > uhub1 at usb1 "NEC OHCI root hub" rev 1.00/1.00 addr 1 > usb2 at ohci1: USB revision 1.0 > uhub2 at usb2 "NEC OHCI root hub" rev 1.00/1.00 addr 1 > ppb5 at pci3 dev 2 function 0 "PLX PEX 8517" rev 0xad > pci6 at ppb5 bus 8 > em0 at pci6 dev 0 function 0 "Intel PRO/1000 PT (82571EB)" rev 0x06: ivec 0x17, address 00:14:4f:d4:d2:c6 > em1 at pci6 dev 0 function 1 "Intel PRO/1000 PT (82571EB)" rev 0x06: ivec 0x14, address 00:14:4f:d4:d2:c7 > ppb6 at pci3 dev 3 function 0 "PLX PEX 8517" rev 0xad > pci7 at ppb6 bus 9 > em2 at pci7 dev 0 function 0 "Intel PRO/1000 PT (82571EB)" rev 0x06: ivec 0x14, address 00:14:4f:d4:d2:c8 > em3 at pci7 dev 0 function 1 "Intel PRO/1000 PT (82571EB)" rev 0x06: ivec 0x15, address 00:14:4f:d4:d2:c9 > ppb7 at pci1 dev 2 function 0 "PLX PEX 8533" rev 0xaa > pci8 at ppb7 bus 10 > mpi0 at pci8 dev 0 function 0 "Symbios Logic SAS1068E" rev 0x02: ivec 0x16 > scsibus0 at mpi0: 112 targets, initiator 112 > sd0 at scsibus0 targ 0 lun 0: SCSI3 0/direct fixed > sd0: 140009MB, 14089 cyl, 24 head, 848 sec, 512 bytes/sec, 286739329 sec total > sd1 at scsibus0 targ 1 lun 0: SCSI3 0/direct fixed > sd1: 140009MB, 14089 cyl, 24 head, 848 sec, 512 bytes/sec, 286739329 sec total > ppb8 at pci1 dev 8 function 0 "PLX PEX 8533" rev 0xaa > pci9 at ppb8 bus 11 > ppb9 at pci9 dev 0 function 0 "PLX PEX 8533" rev 0xaa > pci10 at ppb9 bus 12 > ppb10 at pci10 dev 1 function 0 "PLX PEX 8533" rev 0xaa: ivec 0x16 > pci11 at ppb10 bus 13 > ppb11 at pci10 dev 2 function 0 "PLX PEX 8533" rev 0xaa: ivec 0x14 > pci12 at ppb11 bus 14 > ppb12 at pci10 dev 8 function 0 "PLX PEX 8533" rev 0xaa: ivec 0x14 > pci13 at ppb12 bus 15 > ppb13 at pci10 dev 9 function 0 "PLX PEX 8533" rev 0xaa: ivec 0x16 > pci14 at ppb13 bus 16 > ppb14 at pci10 dev 10 function 0 "PLX PEX 8533" rev 0xaa: ivec 0x14 > pci15 at ppb14 bus 17 > ppb15 at pci1 dev 9 function 0 "PLX PEX 8533" rev 0xaa: ivec 0x16 > pci16 at ppb15 bus 18 > "pci-performance-counters" at mainbus0 not configured > ebus0 at mainbus0 > com0 at ebus0 addr ca0000-ca0007 ivec 0x13: ns16550a, 16 byte fifo > umass0 at uhub0 port 2 configuration 1 interface 0 "Texas Instruments Incorporated 6250 FW: 03.05.02.22.562AD423" rev 2.00/2.00 addr 2 > umass0: using SCSI over Bulk-Only > scsibus1 at umass0: 2 targets, initiator 0 > cd0 at scsibus1 targ 1 lun 0: SCSI0 5/cdrom removable > uhub3 at uhub0 port 4 "Cypress Semiconductor USB2 Hub" rev 2.00/0.0b addr 3 > softraid0 at root > bootpath: /pci@0,0/pci@0,0/pci@2,0/scsi@0,0/disk@0,0 > root on sd0a swap on sd0b dump on sd0b > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From venture37 at hotmail.com Sun Aug 24 17:46:53 2008 From: venture37 at hotmail.com (Sevan / Venture37) Date: Sun Aug 24 17:47:16 2008 Subject: sun4v arch In-Reply-To: <3c1674c90808232348v5f423e31i31c25c8c226291e7@mail.gmail.com> References: <20080824064655.GB11196@booyah.home.comstyle.com> <3c1674c90808232348v5f423e31i31c25c8c226291e7@mail.gmail.com> Message-ID: Matthew & Brad, lets not turn this thread into a cock fight ey! ;) _________________________________________________________________ Win a voice over part with Kung Fu Panda & Live Search?? and?? 100?s of Kung Fu Panda prizes to win with Live Search http://clk.atdmt.com/UKM/go/107571439/direct/01/ From sobomax at FreeBSD.org Mon Aug 25 21:35:18 2008 From: sobomax at FreeBSD.org (Maxim Sobolev) Date: Mon Aug 25 21:35:40 2008 Subject: sun4v arch In-Reply-To: <48B0BEC7.1070806@FreeBSD.org> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> <20080822225510.GI32539@server.vk2pj.dyndns.org> <48B0BEC7.1070806@FreeBSD.org> Message-ID: <48B3259E.8070601@FreeBSD.org> Maxim Sobolev wrote: > Peter Jeremy wrote: >> Is there a summary of the open issues somewhere? There are no sun4v >> PRs open. http://wiki.freebsd.org/FreeBSD/sun4v effectively hasn't >> been touched since November 2006 and suggests that the only critical >> issue is lack of serial port support. > > There is a better interpretation, which is that the only critical issue > is lack of real users for this port, not lack of serial port support :). Just to clarify a bit - my point was not to suggest that port is irrelevant, or that the FreeBSD should not go there. In fact I believe on contrary from what I know sun4v is good as a testbed for the future of multi-processor architectures today - definitely we will see ever increasing number of cores in commodity Intel/AMD servers in few years from now. So that in that sense sun4v work is very important if the FreeBSD project wants to keep ahead of things, not catching-up later. However, realistically immaturity of the port as well as scarcity of hardware limits number of users severely. Therefore, absence of PRs should not be surprising to anyone. -Maxim From peterjeremy at optushome.com.au Thu Aug 28 11:49:46 2008 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Thu Aug 28 11:50:47 2008 Subject: sun4v arch In-Reply-To: <3c1674c90808232139k76f8091bw34aa0f9b71437023@mail.gmail.com> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> <20080822225510.GI32539@server.vk2pj.dyndns.org> <48B0BEC7.1070806@FreeBSD.org> <7d6fde3d0808232039i78fadb9bu7373e1c36f4f37a1@mail.gmail.com> <20080824034055.GB12515@soaustin.net> <20080824042339.GM32539@server.vk2pj.dyndns.org> <3c1674c90808232139k76f8091bw34aa0f9b71437023@mail.gmail.com> Message-ID: <20080828114942.GN33600@server.vk2pj.dyndns.org> On 2008-Aug-23 21:39:34 -0700, Kip Macy wrote: >There really isn't any magic to bringing up a port. You compile it, >install it, and then run it until it breaks. Once it breaks you spend >a lot of time instrumenting the code to track down what went wrong. About what I expected. I've just bumped into your bsdtalk interview: http://cisx1.uma.maine.edu/~wbackman/bsdtalk/bsdtalk086.mp3 This appears to give a useful overview into the sun4v port. One thing you mention is that you'd started work on a virtual network driver. How far did this get and can you point me to the code, It seems that the latest OpenBSD runs on sun4v. I haven't investigated how well supported it is. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-sun4v/attachments/20080828/d35a5425/attachment.pgp From peter.jeremy at alcatel-lucent.com.au Thu Aug 28 22:36:44 2008 From: peter.jeremy at alcatel-lucent.com.au (Peter Jeremy) Date: Thu Aug 28 22:36:50 2008 Subject: sun4v arch In-Reply-To: <20080828114942.GN33600@server.vk2pj.dyndns.org> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> <20080822225510.GI32539@server.vk2pj.dyndns.org> <48B0BEC7.1070806@FreeBSD.org> <7d6fde3d0808232039i78fadb9bu7373e1c36f4f37a1@mail.gmail.com> <20080824034055.GB12515@soaustin.net> <20080824042339.GM32539@server.vk2pj.dyndns.org> <3c1674c90808232139k76f8091bw34aa0f9b71437023@mail.gmail.com> <20080828114942.GN33600@server.vk2pj.dyndns.org> Message-ID: <20080828220500.GC65650@pjdesk.au.alcatel-lucent.com> On 2008-Aug-28 21:49:42 +1000, Peter Jeremy wrote: >It seems that the latest OpenBSD runs on sun4v. I haven't investigated >how well supported it is. It boots but doesn't support virtual disk or virtual network so it doesn't help. -- Peter Jeremy -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-sun4v/attachments/20080828/c45066e9/attachment.pgp From peterjeremy at optushome.com.au Sat Aug 30 08:27:06 2008 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Sat Aug 30 08:27:13 2008 Subject: sun4v status Message-ID: <20080830082702.GL86609@server.vk2pj.dyndns.org> I'm trying to get up to speed with sun4v. Some questions: 1) Is there a more recent snapshot than 7.0-20061112-SNAP-sun4v-disc1.iso 2) Other than the pmap issues (missing TLB shootdowns) what are the critical issues that need to be addressed? 3) What state is the virtual network driver in? I've seen several suggestions that it was being worked on but can't find it in the CVS repo. The virtual network driver is a critical issue for me because I don't have a T2000 or T5xxx that I can dedicate to FreeBSD. -- Peter Jeremy -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-sun4v/attachments/20080830/898110cc/attachment.pgp From kris at FreeBSD.org Sat Aug 30 08:57:16 2008 From: kris at FreeBSD.org (Kris Kennaway) Date: Sat Aug 30 08:57:23 2008 Subject: sun4v status In-Reply-To: <20080830082702.GL86609@server.vk2pj.dyndns.org> References: <20080830082702.GL86609@server.vk2pj.dyndns.org> Message-ID: <48B90B68.80802@FreeBSD.org> Peter Jeremy wrote: > I'm trying to get up to speed with sun4v. Some questions: > 1) Is there a more recent snapshot than 7.0-20061112-SNAP-sun4v-disc1.iso I don't know if there is a newer ISO image. You can cross-build a world and install that though, if you can get it on there (netboot, live CD, etc). > 2) Other than the pmap issues (missing TLB shootdowns) what are the > critical issues that need to be addressed? There might be (probably are) others but it's hard to say until the system is minimally usable. > 3) What state is the virtual network driver in? I've seen several > suggestions that it was being worked on but can't find it in the > CVS repo. I suspect only Kip knows about this. Kris From mat.macy at gmail.com Sat Aug 30 21:18:04 2008 From: mat.macy at gmail.com (Matthew Macy) Date: Sat Aug 30 21:18:10 2008 Subject: sun4v status In-Reply-To: <48B90B68.80802@FreeBSD.org> References: <20080830082702.GL86609@server.vk2pj.dyndns.org> <48B90B68.80802@FreeBSD.org> Message-ID: <3c1674c90808301418n4fa0691fo30d61cc3e6595862@mail.gmail.com> On Sat, Aug 30, 2008 at 1:57 AM, Kris Kennaway wrote: > Peter Jeremy wrote: >> >> I'm trying to get up to speed with sun4v. Some questions: >> 1) Is there a more recent snapshot than 7.0-20061112-SNAP-sun4v-disc1.iso > > I don't know if there is a newer ISO image. You can cross-build a world and > install that though, if you can get it on there (netboot, live CD, etc). Just cross-build and netboot, you'll need to do it anyway. >> 2) Other than the pmap issues (missing TLB shootdowns) what are the >> critical issues that need to be addressed? > > There might be (probably are) others but it's hard to say until the system > is minimally usable. This is the only showstopper that I know of. It can take up to a couple of hours to hit with SCHED_4BSD. The moment you turn on PREEMPTION you'll start seeing seg faults at bootup. >> 3) What state is the virtual network driver in? I've seen several >> suggestions that it was being worked on but can't find it in the >> CVS repo. > All I had really working was the initial bits for registering resources and finding the device handle. I haven't looked at the Linux sources, but they may be a good reference. I can say from having looked that the Solaris sources are *not* a good reference except perhaps to clarify some hypervisor API issues that are ambiguous in the documentation. -Kip From venture37 at hotmail.com Sat Aug 30 21:21:56 2008 From: venture37 at hotmail.com (Sevan / Venture37) Date: Sat Aug 30 21:22:05 2008 Subject: sun4v status In-Reply-To: <3c1674c90808301418n4fa0691fo30d61cc3e6595862@mail.gmail.com> References: <20080830082702.GL86609@server.vk2pj.dyndns.org> <48B90B68.80802@FreeBSD.org> <3c1674c90808301418n4fa0691fo30d61cc3e6595862@mail.gmail.com> Message-ID: the system would flip out when there was even the slightest load on the disk with mpt0: queue full event messages, tweaking the system settings with camcontrol reduced the frequency of this but resulted in dataloss when it did occur http://www.zulustips.com/2007/09/06/mpt0-queue-full-event-on-dell-sas-5ir.html#more-53 _________________________________________________________________ Win New York holidays with Kellogg?s & Live Search http://clk.atdmt.com/UKM/go/107571440/direct/01/ From kmacy at freebsd.org Sat Aug 30 21:25:44 2008 From: kmacy at freebsd.org (Kip Macy) Date: Sat Aug 30 21:25:51 2008 Subject: sun4v status In-Reply-To: References: <20080830082702.GL86609@server.vk2pj.dyndns.org> <48B90B68.80802@FreeBSD.org> <3c1674c90808301418n4fa0691fo30d61cc3e6595862@mail.gmail.com> Message-ID: <3c1674c90808301425i726df580qf1e1e1a56d046ee0@mail.gmail.com> Hrrm, that is a new problem (in the sense that it didn't happen back when I was working on it). Sounds like a scheduling issue. -Kip On Sat, Aug 30, 2008 at 2:21 PM, Sevan / Venture37 wrote: > > the system would flip out when there was even the slightest load on the disk with mpt0: queue full event messages, > tweaking the system settings with camcontrol reduced the frequency of this but resulted in dataloss when it did occur > > http://www.zulustips.com/2007/09/06/mpt0-queue-full-event-on-dell-sas-5ir.html#more-53 > _________________________________________________________________ > Win New York holidays with Kellogg's & Live Search > http://clk.atdmt.com/UKM/go/107571440/direct/01/_______________________________________________ > freebsd-sun4v@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-sun4v > To unsubscribe, send any mail to "freebsd-sun4v-unsubscribe@freebsd.org" >