Back in 2000, when I moved from Brazil to America to US, I was 42 years old and my weight was around 220 pounds. But during the period of 14 years, I gained a lot of weight mainly to the fact that here we eat much more food. The fact that I didn't do any physical activity to offset this, I started adding weight and like I said in 14 years I moved from 220 pounds all the way up to 310 pounds. That's when I decided that this thing should stop and I should change the way it was going to. With the weight gain came a variety of health issues. The most critical one was type 2 diabetes.  I had sleep apnea and this whole thing was adding up to a point that I could not manage anymore. I chose to have the surgery at the Michigan Medical Center in Midland because my colleague at work had the same surgery with the same team. He was very successful in his surgery and I was impressed with the results. I went to attend a seminar and one of the coordinators explained us how this thing works and several different options of surgery. I chose for the leave gastrectomy because I found during my research and conversation with the doctors that would be a more definitive solution compared to the other options. Even though all of them have their benefits, I chose to be more radical and say, okay, if I have this leave gastrectomy, it's kind of a no way back. So I would reduce my stomach size, I would be forced to eat less and more frequent and I would have to be educated in terms of what kind of food to eat and eat more health and etc. So that was what I decided to do. A couple of months later, around July that same year, I found this Taekwondo school in the Midland Mall and I decided to join and to have an activity that I could commit with time. It requires certain abilities in terms of agility, flexibility, elasticity, dedication, all of these together with physical feet preparation and during my tenure of being prepared and moving from belt to belt to belt, I saw other people that was part of the group that I go in the school going to competition and we have this group going right now. We have nine students and four or five of them came from the bariatric surgery so it's very, very, very rewarding. The surgery changed the way I eat primarily by limited the size, the amount of food that I can eat. For me, having the bariatric surgery was the best thing that happened in my recent life. I was going, like I said, in the wrong direction and bariatric surgery put me back on track to be healthier, to remove all of those health issues that I had. And today I'm a healthier person. I'm happy. I like the results. If I have to do it again, I definitely would do it again.


Hello everybody and welcome to another hobby cheating video and this is going to be an unusual one because it's quite product specific, but I'm really excited about this product and I wanted to share with you all the different ways we're going to use it. This is all about Green Stuff World's Pure Pigments Metal Pigment Set. Now I already did a product review on these so that you can find up in the corner there if you want to go check that out. I covered the basics like why I'm putting this together with metal varnish and stuff like that. This is really the video about how to use it. So here we have a little old school horsey, he has a lot of metal armor. I have some mixes of the antique gold, regular gold, bronze and then the copper. Those are all mixed with the pure pigment mixed with the Vallejo Metal Varnish. So we're just going to go ahead and get some of that going and we're just going to give it a nice application. Now one of the reasons I picked this Goofy Old Miniature is because it's both white which is generally terrible for metals and then it has other weird colors on it and I wanted to show you just how fantastic the opacity is of this. This is one smooth coat, goes on like butter like painting with gold flake or something and the sheen on it is just, it's out of this world. So you can see you get a nice smooth application. You have quite a bit in your brush usually. It's quite tough because you've got varnish mixed in with it so you get a really, really shiny surface that's also quite durable and resistant which is great. So this first part is really just base coating. I just want to show you how smooth the application was, how easy it goes on. It's really no problem and all the different colors will work just as well. All of them have about the same amount of coverage so for example here I'm going to use that lustrous wonderful red copper and you'll see that that as well covers all the same. Just some quick notes. Obviously this is metallic, don't lick your brush or anything like that. These pigments are made of real metals so you know that's not good for you but other than that it's so smooth it goes on like a dream and as you can see it covers everything in one quick coat. So enough of that let's get on and do some interesting stuff with this. So the first mixes I made were pretty straightforward. Just that plus the varnish to get a straight gold but I made a couple of the little piles of the pigment here and you can also mix it with other things. So here I've got some Scale Color Ink Tense Chestnut. I could also use Dollar Rowney inks or Vallejo inks or anything like that and all of those would work just fine. Now I'm using quite a lot of ink here. I got a little drip in my other pool like a dum-dum but that's okay we'll fix that later. And at first when you're mixing it it's looking like okay but it's the same gold but just wait. As I continue to mix it you're going to see that ink take over and fully mix in there and what you get is this really nice deep brown gold. Now I made this really extreme. The advantage here is it will be quite thin but it's still got the metal pigment in it. You could do this with any color ink. I'm doing it with brown because I'm going to show you as a shade on the existing armor but you could if you wanted a really lustrous red gold. Great just mix some red ink right in. As we'll see later you can also paint right over the top. But this is a great way to get your shade color for your metals because it's naturally quite thin because you have such a high amount of ink in it and it's got the same color gold in it so it's going to blend right into the miniature itself. So if we grab our little horsey back here after I try to wipe that away and fail horribly it doesn't matter I fix it in between the next shot. You're going to see how you can just easily get some nice shadows or tones or variation on there without any kind of issue. So we're just going to lay that shadow right in there nice and smooth and just like we basically applying our normal tactics of painting metallics in a non-metallic style and you can get really soft easy subtle shades worked in there to play with the tones of the metal. And it just takes that so well see how that provides that nice additional deep color. Mixing in inks with the pigment really gives you because you can just keep applying the inks you can do a little less a little more crank up the intensity. It just really makes for a wonderful way to work with metallics and to increase your contrast of value on something that's already quite reflective but brings the light back under control. All right so now we made a shade let's go the opposite direction. I've still got my other little area of pigment didn't mix with the brown clearly. Now I'm going to take some Vallejo acrylic metal color silver that's right a different metal paint a silver metal paint. The magic of these pigments is that remember they're going to mix with anything that's got acrylic medium or alcohol for that matter quite easily because it's just pigment. And here what I'm going to get is a nice thin ultra bright silver highlight. So you can actually mix in your brighter color metals add a little bit of this into the pigment and you get a hyper hyper reflective gold.  This is an easy solution. If you drop silver into your into with some gold pigment and boom you've got a perfect silver highlight. Okay you'll notice with all these I do mix them extensively that's intentional. You do want to make sure that pigment is completely mixed into whatever you're working on. So with that done let's go ahead and get that onto our horsey. So now we're just going to reinforce those highlights basically right where the light area is hitting so we get a nice clean bright reflection. And yet again you can see just how easy it is to work with like I turn the brush sideways to hit the edge of that and it just hit the edge perfectly.  It's really nice. You can mix it back in create a half step if you want to bring it you know again smooth it back in mix it in with the other colors whatever you need to do very very easy to work with. Alright so I put some paint on the rest of the horse just so we can you can kind of see what it looks like.  We don't have to stop there so here I've grabbed some Blood Angels red contrast paint but you could also use Tamiya X27 clear you could use again normal inks any kind of highly transparent thing like contrast paints ghost tents dollar roundy inks Tamiya clears whatever. This goes over this so wonderfully well if you love the idea of sort of metallic sheen Blood Angels or sort of the 30 K style of vehicles where they have that red over the sheen this gold is so wonderful to work with that kind of a technique because it's got such a high luster that it really shines through and here I'm using the contrast paint straight normally I would thin it down if I was going to do this but and I would recommend you actually do thin it down a little bit if you're trying to do this technique but I wanted to just display to you how strong and shiny the luster of this this gold is even through that red absolutely wonderful so in any way you'd want to use this this true metallic paint the key is you can mix it with varnish to get it straight you can mix it with inks to change its color or or contrast paints or anything like that to change its color to create shadows for your existing color or simply to do colored metallics you can also mix it with silvers if you want to create really shiny bright versions of it and of course you can paint over it easy enough if you want to have that kind of a sheen over all of your colored sort of metallic where you've got a bright color reflecting highly through something else over top but any kind of ink will work you could put you know like I've got here these Vallejo inks you can use that straight over the top you could do the coloration through an airbrush as a glaze you've got options so there you go give it a like if you liked it subscribe for additional hobby cheating in the future if you've got questions drop them down below but as always thank you for watching we'll see you next time


So, we have a circle here and we will divide this circle into few parts and our objective here is to find out the area of the circle or rather visualize the area of the circle and there is a very interesting way in which we can do that. So, I have divided the circle into eight equal parts now. I just want you to focus on one of these parts just color it and if you just look at this pie this resembles a triangle and let me color the other one what I will do is I will arrange these two pies and this is how the two pies when arranged together will look like. Now if I arrange all such pies so if I arrange all the eight pies side by side this is how I will be able to arrange all these eight pies. Now notice one thing the boundary of all these pies together is equal to the circumference of the circle. Now if the radius of this circle is r then this side length is also going to be r now because the circumference of this circle is 2 pi r and the total boundary of the pies also constitutes to be 2 pi r half of it is above half of it is below so then the total length here is going to be pi r and the same thing will be here. With this particular diagram where this looks like a rectangle where one side is r and the other side is pi r how can we make sure that the area of this shape indeed is equal to area of the circle what we do is that we want to divide the circle in more and more parts look what happens when we divide the circle in more and more parts as the number of pies increase there will come a point when this curvature here will reduce and it will seem like it's a straight line as we keep on increasing the number of pies and as we increase this number of pies this length of the radius will also decrease and it will become more and more straighter and so ultimately in the case where we have infinite pies we will be able to approximate the area of a circle by a rectangle of side r and pi r and the area of this rectangle is r times pi r which is pi r square and therefore area of this circle is also pi r square.


The India-America strategic partnership is in the true sense a partnership of trust. Our common interests in defence and other matters and our shared values have indeed strengthened this bond of trust between other countries.


Hi, all welcome And thank you for the introduction. It's great to be back at a Linux security summit and I wanted to take the opportunity today to Kind of give you guys an update on what's been going on with AMD's secure encrypted virtualization or SEV feature both what we have been doing within the last year and Kind of some of the things that we're looking at in the near future as far as open source support goes So for anyone who's not familiar with this feature, this is a technology that we introduced about a year ago now into our server line of x86 chips and the SEV feature is designed to offer protection for virtual machines from the hypervisor and so this is kind of a change in the traditional trust model of virtualization and and There's a number of potential scenarios where this is interesting kind of the most obvious one is a public cloud type scenario and Where we have this situation where From the guest perspective, so kind of the cloud customer, you know, they they want to to use a cloud But they see the potential risk of the hypervisor and the access that it has Obviously the hypervisors code that they are not able to control directly But the customers have various obligations including sometimes legal obligations to protect the data that they're working with And so that's concerning and on the the hypervisor say the cloud vendor side, you know It's a similar situation. They want to be able to offer more security to customers and really In general, they tend to see the visibility as more of a liability That is the the visibility they have in a customer data as a liability that that They are concerned if someone comes asking for that You know, that's not really what they want to be providing And so the the net result here is that, you know, we believe there's this opportunity to Try to offer some security enhancements in this space So the AMD SEV feature is designed Primarily to protect against two different classes of attacks on the one hand. We have physical access attacks, which means someone is kind of physically on the motherboard and they're probing the DDR bus or They're doing a cold boot attack or something like that. And so Because we have Memory encryption is part of this feature then we can offer strong protection against that We also are offering protection against certain types of admin access attacks. And so this is like Someone with root access trying to do a memory scrape of a guest Trying to inject code Into that guest to get it to execute that or just as kind of an extra layer of resiliency Against a potential hypervisor bug or side channel attack or something like that that can potentially allow One guest to escape its sandbox and try to see what else is going on and So just kind of at a high level the way that this feature works. There's a few components This is rooted in something called the AMD secure processor, which is kind of a security subsystem That's embedded in our SOC. It's got an arm core on it. It's got some private resources and this implements the key management and For the VMs it provides an API for doing VM lifecycle management and So this API has things to help with starting these encrypted guests generating attestation reports Assisting with migration things like that. This is publicly documented. We have a spec on our website that details this and from the Kernel perspective the secure processor just looks like a PCI device. So it has a standard MMI interface and This API is intended to be called from the hypervisor as it's doing these various lifecycle tasks So the hypervisor is responsible for still managing the resources in the system calling the various functions that it needs to on the secure processor and Then within the guest we have support for the SUV feature within the OS kernel And this is primarily because there is a new x86 page table bit that's defined as part of this architecture and That bit allows the guest kernel to indicate pages of memory that are to be marked private meaning that they're encrypted with the guest specific key and shared versus shared pages which are accessible to the hypervisor and so the way this Set up today in Linux for instance is that the vast majority of pages are marked as private Except for a few pages that are necessary for either para virtualization features or things like DMA So the nice thing is that once we have that support within the guest kernel There's no application changes that are necessary so all the applications within the VM just run as normal and they just default to using encrypted memory and And Kind of an example support environment for this today We have supporters. I'll get to it in KVM QMU And then we require using OVMF as the BIOS within the guest VM to help to bootstrap that and And I say this is this is now commercially available So I've got a Brief demo video of how this works and hopefully this will this will play But essentially the setup here is that we've got a server. It's running two different virtual machines one with this feature turned on and one with it turned off and We've kind of made it pretty with a little website here, but essentially these are Just commands that someone with with root access on the box is able to execute and so If we play this Yeah, so we have just looking for a QMU process and then pulling up the memory map for it and Then just dumping the memory with a DD command and So the first page of memory is is mostly zeros so that's that's of course as expected if you do the same Same Same thing but with a VM that has been run with this encrypted virtualization feature So we have that on the right side here We do the same thing and the data is Essentially random and that's because the hardware is aware that we're running in the hypervisor mode versus a guest mode It only allows access to the key when it's running in get in this particular guest and so when you try to view that memory from outside then then you just see the cipher text and So then what this is going to show is Just a text editor. So this is like a user editing file in that VM. It's just sitting in memory it's not actually written to disk yet and the the admin user on the on the Native box that's running these is going to basically do a grep command on the memory and Of course on the left side. It's very easy to find the text. That's it's in this file and When they do the same thing on the right side then They find nothing and so, you know, this is about as exciting as a security demo get so that's that's what we got And this is this is a two gig Of ram guest so as you can see it's pretty easy to do it. It's pretty fast Okay, so what's been going on in the last year as far as this feature goes so The main thing is that we've been starting to upstream support for this feature as well as We have the SMU which is secure memory encryption feature, which is a simpler form. That's just Memory encryption support for a native system And so we we have support for that starting in in 414 and then we we kind of had two sets of patches for the scv support so we had the Guest patches that made the kernel aware of this new page table bit so that it could be run inside one of these VMs that went into 4.15 and Then the KVM patches that interfaced with the secure processor and did all the Appropriate management for these VMs went into 4.16 And so depending on when some of the recent commercial distributions picked up their kernels There are certain ones that are capable of being run out of the box today as either an scv guest or an scv hypervisor We do have a website that I'll mention a bit later that has kind of getting started instructions for each of these distributions So if you're interested in kind of playing with this and want to know the Options to give the QMU and all that stuff. We do have that documented The other thing that we've just gotten up fairly recently is just some enhancements to the vert.io GPU support we had basic vert.io stuff working initially, but there's some rearchitecture of the GPU driver that was needed to Work with how DMA works in the scv world. And so so that was recently completed and And so that's kind of where Things are right now What we're gonna be working on here in the very near future One thing is migration support for these guests. This is something that is supported in our secure processor API We actually do have prototype patches available today on our public github page if anyone's interested in trying those out So we're gonna be working on getting those upstream. I think right now they need some optimizations So we're gonna do that. We're also looking to open source something we call the scv tool very shortly and and this will also go up on github and this is really just kind of reference code for parsing attestation reports validating certificates things like that so All the formats are documented, but hopefully just some reference code will be helpful for anyone trying to use this We're also gonna be doing some support for kind of save and restore of these virtual machines and Then the other big thing I'm gonna talk about more here in a sec is Support for a feature we call scv es Which is our scv with encrypted state support and so this is kind of the next major feature in the the scv roadmap So the es feature I talked in more detail about this last year at the North American Security Summit And this is also a feature that's available in hardware today. It was it was shipped as part of the Initial launch we did last year and The idea with this feature is to not only protect the memory space of virtual machines But also to protect the register state across world switches so There's two main things with this feature The first thing is that there's now hardware support for kind of this really large atomic world switch operation so We've expanded what we call the VM CB which is the structure that holds all the register state for the gas to Contain basically everything that's needed. So gpr state floating point state and so on and there's a single Atomic switch that happens between the hypervisor mode and the gas mode and Then and that structure is now encrypted so the hypervisor cannot actually see what the gas contents are across these world switches The second piece of this is that for the cases where the hypervisor does need to be involved in emulation for Mio or or certain instructions We have a new exception that we call a VC or a VMM communication exception and The idea is that when the guest does something that needs support like a CPU ID The hardware throws this exception and the exception handler then does this para virtualization thing with the hypervisor to To process that and I'll talk about that in a second This communication is done using a structure called the guest hypervisor communication block Or a GHCB and this is a new thing that that we're adding so With the ES architecture we have divided the types of VM exits into two categories So we now have this list of we call automatic exits Which are the only things that actually cause you to exit a virtual machine and go back to the hypervisor And so that's things like asynchronous interrupts certain instructions like halt and shut down certain types of page faults and Then everything else which is the vast majority are these non-automatic exits Which are the things that cause exceptions within the guests. So I said you got CP ID You got your MSRs. You got your IO ports, whatever the hypervisor is choosing to intercept instead of actually Intercepting back to the hypervisor. It now produces this exception in the guest and So the way that this works is you know the guest starts by doing something Say like a CPU ID and now instead of doing the exit. We'll get this exception So in response to the exception, there's this new handler inside the guest VM. That's going to Read this error code. It's going to see oh, I try to do a CPU ID I need to Write some information to this GHCB structure to tell the hypervisor I want to do a CPU ID and so it's going to do that and it's going to do this new instruction We've added called VMG exit, which is basically a hyper call In response to that. We're actually going to completely exit the guest We're going to save the state and crypt it we're going to go to the hypervisor The hypervisor is going to read the GHCB. It's going to see we want to do a CPU ID But instead of actually writing the results directly into the registers for the guest it's going to write it into this GHCB data structure and It'll then resume the guest where we go back to the handler And so the exception handler will see these new values it can decide if it likes them or not if it thinks they're safe and It can then copy them into its own register state and it can go back to the guest so the basic idea is that all of the Kind of intercept behavior things they all get funneled through this centralized exception handler So the rest of the code whether it's in the kernel or in user space doesn't have to be aware of the security feature so one of the One of the piece of feedback we got very early on with this was that it would be really nice if there is a standard protocol for doing this para virtualization stuff between guests and hypervisors regardless of vendor and And so we decided to take on the challenge of trying to standardize this and And I mentioned this last year as well, and I honestly hoped that we would be a little bit farther along than than we are today It's not anything to do with this feature It more has to do with the fact that many of our security and kernel developers We're kind of busy earlier this year. You guys might know why so But the good news is that is that we are coming back to this so just last week I believe we posted publicly a copy of we call the ghcb software specification It's not that long. It's less than 20 pages. I think and This is kind of our first draft of our attempt to standardize this and so this is open for feedback there should be a mailing list thread on this pretty soon and And and we've been shopping this around both within the open-source community as well as with the proprietary vendors and The the specification here it defines a few things of course defines what the the memory of this structure looks like It defines which specific exceptions guests are expected to handle and That's because there's a lot of potential intercept bits in our architecture, but most of them don't need to be set and so we're defining exactly what the minimum subset is that's required for support and With each of those we're defining what values the guest is expected to provide for the emulation and what the hypervisor expected to provide back And then there's also a few things in here about how we do bootstrapping And how we we bring up multi vcpu environments NMI handlings and other kind of weird oddity and so what we're really hoping to do here is to provide this unified interface so that Your guest OS can boot and doesn't have to be aware of exactly what hypervisor it's running under things like that so if you look at the document what you'll see in part are a number of Entries like this that basically say Okay on this particular type of exception. How does the protocol work? So for instance if the guest does a read MSR instruction it will generate this exception and then the guest is expected to set a few fields in the GHCP structure to say You know, I want to do a read MSR and here's the RCX values so indicating which MSR I want to read and in return the hypervisor supplies Rax and rdx similar for CPU ID. There's different things Really one way to think of this is it's basically a sparsely populated Register state structure. So just instead of everything being supplied Only the values that are actually needed are being supplied to the hypervisor so As I mentioned feedback on this is welcome. We started receiving some feedback already That I did want to share You know, there's been a few things that I think have gone pretty well. I've actually been pretty impressed with how well Kind of people have worked together as far as both the proprietary and the open source community So so I think that's really great In the current specification we have the layout of the GHCB matching that of the legacy MCB so basically the state structures look the same And so that's really helpful from a compatibility standpoint because they can use the same memory offsets everything It also turns out that there's quite a lot of similarity across hypervisors in terms of which Behaviors need to be intercepted and how those intercepts need to work and that kind of makes sense because it sort of falls out of the x86 is a quite a bit and In this type of a virtual machine environment the hypervisor really has to be very hands-off It has to let the guests run as much as it can until it does something that it really has to step in for and so Because of that we see we don't see much variation here and And also the way that we negotiate this protocol So we do have this version so it can evolve over time and there's a way that as the guest boots It can find out what version the hypervisors supports and respond accordingly There were a few interesting challenges that we did discover during this This initial review and I say we're just getting started on this one is so there's this VMM call instruction which is traditionally used for hypercalls and Of course it kind of makes sense that different hypervisors would use VMM call for different things What we also discovered is that their calling conventions are completely different and there's no way to make them mutually compatible So we basically had to throw our hands up on this one and we basically said that you know Look, you're gonna have to customize this particular behavior depending on your hypervisor We also had some some challenges around things like AP startups So this is how we boot the other vCPUs if you have multiple cores within your guest Traditionally this is done using a inter-process interrupt or an IPI which tells the processor is where to go and start executing but We don't want the hypervisor to be able to supply an arbitrary instruction pointer for them to do that So we kind of had to rework this protocol a bit where the hypervisor can wake up a core and then the core has to go and get its actual Jump address from its encrypted memory So this is kind of a new protocol You know we have a prototype. I think it works. This would be be something to review and Then we have a few other things that are really not supported in the current spec So hardware debugging is is not really supported many you are probably aware of a couple years ago There's a CVE about how Hypervisors have to intercept debug traps because otherwise the guests can spin forever There's kind of a processor deadlock situation that can happen and they can do a denial service And so because of that we're not really able to make use of these in one of these isolated guest environments We also don't have support for SMM today and I hope that stays that way, but we'll see So the the final thing I just wanted to mention is kind of an update is We have started looking at ways to leverage SEV support with containers and so we started to get involved a little bit with the Cota container project and This is a project that Works on running containers using hardware virtualization And it uses kind of a stripped down version of the Linux kernel I think based on clear Linux and we have been looking at ways to enable the SEV functionality within that project and It turns out that's actually not too difficult because the kernel support that we're already upstreaming kind of flows into that with some modifications to the runtime and You know the way this works is very similar to a normal container. It's just that there's a new option for specifying an SEV runtime and When you do that then you get a Container that's that's using this feature and if you were to look at the memory from outside of the container It would be the same as that video that I showed earlier that it would all look to be encrypted because it's in a VM So this is not upstream yet but we do have We do have that those patches on our public github page So if that's something you're interested in playing with I would encourage you to check that out So, you know overall we're we're making progress around SEV Where we have a few areas that we're working on and the encrypted state feature is kind of the big one that I'm hoping we're gonna make quite a bit of progress on within the next year and In part of that is trying to standardize this interface between guests and hypervisors and so I hope that works out We do have a new Developer dot AMD dot com page. So that's got links to all the specifications related to the SEV feature as well as We have a public github page that has kind of getting started instructions for if you want to start running some of these encrypted VMs You right now a lot of it's still script based. We don't have any nice GUIs yet, but I'm sure you guys can figure it out and And and as I mentioned, there's a tree on there as well with some of the kata stuff if you want to play with that So that's what's been going on any questions I haven't worked with AMD yet, but I worked with trust zone a ram trust zone. So you mentioned before All registers state so the question I trying to understand the difference Could you please define the all register state and second question is Why do we need to encrypt those? When we do is when do and do a switch because usually One shouldn't have access to in different Registrate state as I understand and the third question is if they encrypted where This encrypted state is stored or kept. Yes. Thanks. So if I can remember all three of those So the the register state so it first of it specified in our public x86 doc So if you want the full list you can look through that but essentially It's all the all the VM state that used to exist. So kind of the basic control register or segment state It's all the general purpose registers. It's all the floating point registers And it's a certain set of MSR is related to like system call behavior and things like that The register state is encrypted so that the hypervisor or somebody with root privileges not able to see it and gain information from that For instance, if you are there can often be privileged information in registers Like if you're using the x86 AS instructions The key for your AS operation is actually in one of the XMM registers in the floating point unit And so, you know, that's something that we would ideally not to just have their sitting in memory If you take a and say interrupt while you're in the middle of an AES operation The the data itself it's stored in in normal memory There's no special location for it. It's just that it is encrypted with the guest specific key So it looks basically like any other page of guest memory if the hypervisor tried to read it So it just sees the ciphertext Thanks, sure Thanks for talk first. Is it the actual contents of guest memory access accessible through JTAG so on our parts When when parts are configured for production the JTAG interface in general is blocked off. So There is no JTAG Debug support at all on a production AMD part So so no Okay, and second does it something does it this feature some has something to protect against side-channel text or Make it more difficult Yeah, we don't have any specific side-channel protection You know the the one thing that we're able to offer is just because the the memory space is encrypted with kind of a per guest key You know if you have say a side-channel that lets you kind of read memory with hypervisor permissions You can't use that to see the plain text of another guest right because the hypervisor normally can't see the plain text of other guests But there is nothing specific for like side-channel attacks within a guest or anything like that and What about CPU caches? So in terms of the security or the side channels or So the way that this works with the caches is that each cache line is tagged with the address space ID that the cache line belongs to so The data in the cache is stored in the clear But it's tagged with the owner of that data So only that VM can access it if the hypervisor tries to read that same address We'll treat that as a cache miss because the tags don't match so There is no way to Kind of leak data directly through the cache But as far as kind of general cache side channels, I said we don't have any specific features there Thank you So other than the GMC be registered state most of this seems to be about Confidentiality rather than an integrity of the system. Is there Anything that prevents the hypervisor from say replaying the same Like snapshotting a page running the guest for a while and then replaying the old encrypted page Yeah, so in general in this generation the answer is no That the memory is it's just Encrypted it's not integrity checked. We do some integrity checking on the state page specifically Because we see that as being kind of an easier target for that. So there is some protection there But in general, you know rollback attacks are not not blocked today Okay, so is it fair to say that in the present generation? This isn't a protection against an actively malicious. That's correct. Yeah There's questions up over there Well, I had two questions in the previous was the first question. So I won't duplicate it Is there any relationship to any TPM? Keys and the keys inside the VM. I know that you guys have a TPM in SCP So is there any relationship at all between the keys and the association between a key that might belong to that application to Yeah, there isn't today, you know the the functionality that the secure processor provides certainly has some similarities to a TPM in terms of the way that when you set up one of these things you basically do a measurement of the initial biosimage and That gets turned into basically attestation report for the guest but it's not a TPM specific interface and today we don't have a way for the guest VM itself to actually call any services on Secure processor. It's only there for the the hypervisor to use So if the guest wants a TPM like functionality, it basically would have to provide it itself and software But your scp. I thought implemented a TPM as well. So inside the same space Yeah, so in our client generation of parts we do support we call firmware TPM So we basically emulated TPM 2.0 We don't support that in our server line of parts, which is the the line that supports this feature that that's mainly because We do is kind of a cost-saving measure and for server the cost-saving isn't as important And you know the firmware TPM is not certified like a discrete TPM is Unfortunately, I think I have to stop for discussion, but the good thing is now the coffee and tea break is there So I think we can maybe continue the discussion there. So let's thank David for the talk


The Anchorhawking Glass Corporation brings you crime photographer. What's puzzling you, Ethelbert? One of those quizzes, and it says here, uh, what are these men famous for? Sidney Porter, Samuel Clemens, Charles Dodgson. Well, they're all great authors. Well, how come I never heard of them? Well, you would if they printed their pen names. They're O'Henry, Mark Twain, and Lewis Carroll. Well, I'll be. Those names are famous. Everybody knows them. Like everybody knows Anchorhawking. The most famous name in glass. Ladies and gentlemen, this is Tony Marvin. Every week at this time, the Anchorhawking Glass Corporation of Lancaster, Ohio, and its more than 10,000 employees bring you another adventure of Casey crime photographer. Ace Cameraman, who covers the crime news of the great city. Written by Alonzo Dean Cole. Our adventure for tonight, the Serpent Goddess. Around two o'clock, a sumptuous suite in one of our city's finest hotels. There's a knock at the door, and a big, weather-beaten man opens it. I guess you're the newspaper folks have found me. I'm Dan Sykes. Ah, thanks for giving us this appointment, Mr. Sykes. This is Miss Williams. My name is Casey. Oh, I'm real pleased to meet you, Miss Williams. Thank you, Mr. Sykes.  Thanks again. Come in and make yourself at home. Thanks. Well, what can I do for you? Well, through a mix-up, Mr. Sykes, our paper didn't have anyone at the airport this morning to cover your arrival with Mr. Johansson. And the Morning Express wants to rectify its blunder now with a special interview. Pictures too. Take all the pictures you want and ask all the questions you want. We'd like to have you partner Mr. Johansson in on this. We phoned him, but he wasn't in. Oh, Chris went out to look for a cheaper place to live. He ain't like me. I'm going to enjoy my dough. According to our new service reports, you and Johansson have already sold part of the emeralds you found in South America for over a million dollars. That's right. I'm a nouveau rich. But we didn't sell the best ones. We brought the eyes back here to the States with us. The eyes? Well, that's what Chris and I call the two big emeralds we found. Reports on how you found all those emeralds have been rather conflicting, Mr. Sykes. What's the real low down? Well, Chris and I were flying an old crate out of Caracas on our way to Lima when our gas line broke and we had to bail out over the jungle. While we were trying to find our way out, we come under some ruins of an old engine town and under a stone we accidentally knocked over, we found their emeralds. And that's all there was to it. There wasn't another man with you and Mr. Johansson? No, we were alone. The first story we got on you, fellas, was a two very sick man, one with a pocket full of emeralds, had staggered into a village at the edge of the jungle, raving about a third guy they'd seen crushed to death by a big snake. A huge boar, constrictor, or an anaconda with, of all things, a human face. Well, actually, a yarn like that made news. One of them South American reporters dreamed up that crazy stuff. Whoever saw a snake with a human face. Excuse me, someone at the door. Oh, hello, Chris. I think I find me a place to live, Sykes. But such high prices? Oh, you've got company. Well, they're newspaper folks. This is Chris Johansson, Miss Williams. How do you do, Mr. Johansson? Well, you are a pretty lady, Miss Williams. And this is Casey. Hello, Mr. Casey. How are you? They've been interviewing me about our emeralds, Chris. I'd just been telling them that snake story was a lot of bunk. Yeah. Sykes and me was alone in that jungle. Also, we are not afraid of no drums. Drums? One of the goofy stories they told about us was that when we come out of that jungle, we raved about hearing drum beats all the time.  We didn't know what we were saying. We never said anything about drums. No, we never said nothing because we had no reason to. That's right. Well, I... I'd like a drink, Sykes. I see you've got the bottle there. Help yourself. Well, what other questions do you want to ask, Miss Williams? I'd like to know. Sykes, a drum. It can't be here. Oh, not in a city. It can't be here. What's the matter with you, fellas? Nothing. Nothing. Oh, there's music now, Chris. Look out of this window. There's only some Salvation Army folks down there with a bass drum and a couple of horns. Yeah. Yeah, just Salvation Army people with an ordinary old bass drum. Good night, Mrs. Whalebrecker. Now, Casey, what was I saying? Saying good night to Mrs. Whalebrecker. Oh, I don't know, Pat. You hadn't started to say anything yet. Hadn't I? No. Oh, I remember. You know that fellow Sykes who you and Miss Williams told me about interviewing a couple of weeks ago? Mm-hmm. Well, he'd come into this bar today and I served him a couple of drinks. I recognized him immediately from the pictures you took for your paper. After the little blonde, he had with him called him Dan Sykes. No, afterwards.  Mm-hmm. A few days ago, we saw him with a big brunette. Well, he told us he was going to enjoy his dough, Annie. He's a awfully nervous acting guy, Casey. Walter happened to hit the bottom of empty wooden ice tub. He was taken down cellar. And when it went boom like a drum, I thought Sykes was going to faint that away. Yeah, he and Johansson are certainly allergic to drum beats, aren't they? They didn't give you no idea why. No. Their only explanation was an obvious phony.  Well, it's a good reason to believe that a third man may have parachuted into the jungle with Sykes and Johansson. Yeah? According to Inside Dope, our paper can't print without risking a libel suit, Sykes and Johansson use their plane for smuggling jobs. And it's thought they specialized in smuggling people from one South American country into another. Like wanted criminals, red huts. Yeah, and political troublemakers. It's suspected that Sykes and Johansson were taking an exile revolutionist back to a country he'd been kicked out of when their plane went bad, and that he's the other man they talked about when they came out of the jungle. They were both delirious and fever then, but when they recovered and knew what they were saying, they quickly changed their story. You figure they told the truth while they were delirious. Well, they couldn't help it. Then it must have been true about the third guy getting crushed by a big snake, but a snake with a human face. Yeah. Oh, we can't worry about it here any longer. Casey, we've got to get back to the office. Yeah, yeah. Four city desks starts paging. What do I owe you, pal? Uh, it's only, uh, 60 cents. Oh, only 60 cents. That's too bad. I guess I got that much. Oh, excuse me. There's the bar for... Hello? Uh, just a second.  Huh? Oh, give me. Oh, this is Casey. 301 Hawthorne Street, apartment 3A. Okay, I got it, Burke. Oh, what goes there? Who? Say that again, Burke. In a city apartment? Hey, that's a story, all right. Look it right up there. Hey, what is it, Casey? You look funny. Chris Johansson has been found dead in his apartment. Sykes Park? Yeah. Annie. He was crushed to death. Crushed, squeezed. As though a big snake had coiled itself around him. The story will continue in just a moment. To you who enjoy good wholesome American beer and ale, here's the easiest, most convenient, and most satisfactory way to buy it. Ask for your favorite brand in the new Anchor Glass One Way No Deposit bottle. Now, here's a bottle made just for you. No one has ever used it before. No one will ever use it again. And it costs so little that it can be thrown away when empty just like any other food container.  And though it holds exactly as much as the regular beer bottle, the One Way bottle is so compact that it takes up a minimum of precious refrigerator space. It's light and easy to carry. It chills beer more quickly and holds the chill longer. It looks well on any table. But most important of all, it's made of glass. And because it's made of glass, it brings you beer and ale of perfect clarity, untouched by any foreign flavor. The Anchor Glass One Way No Deposit bottle is a product of anchor hocking. The most famous name in glass. Captain Logan, did the medical examiner say that a big snake? He didn't say a snake did it, Miss Williams. He only said that a python or boa constrictor were the only things he knew of that would kill in such a way. Johansson was literally squeezed to death by something big and smooth that coiled around his entire body. In this apartment? Yes, Casey. What do you think, Captain? Only that a snake big enough to do the killing didn't do the killing. That's too crazy, Miss Williams. Oh, not Casey. I just can't figure this one out at all. You know about the first news story about Johansson and Sykes, huh? Yes, I think you told me about it, but that fantastic yarn can't have any bearing on it. Naturally, you're going to question Sykes. My men have orders to bring him here as soon as they can find him. Here's your Sergeant, now, Logan. Now, maybe now we'll get the load out. You found Sykes at his apartment, Sergeant? Yes, Captain. I gave it to him cold about Johansson's death. I thought he was going to pass out on me, especially when I told him it looked like the job of a big snake. He kind of whispered to himself, she followed us. She followed us? Yes, sir. Well, were you able to find out where he was last night when Johansson was killed? Sykes was throwing a big party in his place. His alibi is perfect. Now, bring him in. Yes, sir. She followed us. That's a screwy one, Casey. Yeah, another screwy one like his fear of drums. Mr. Sykes, sir. Oh, I'm Captain Logan, homicide bureau, Mr. Sykes. You already know Miss Williams and Mr. Casey? Let me see, Chris. Now, the body is still in the next room where it was found. Now, step in. Take a look. So that's what she does to our man. Who is this she? Let me out of here, Captain. I can't look anymore. Now, let's go back into the other room. Sit down, Mr. Sykes, and tell us what you know about this thing. I may as well tell you that I know now there's no way of getting away from her. Vasco said we couldn't. Vasco? She got Vasco first. Now it's Chris. Soon it'll be me. You explain what you're talking about? Okay. There were three of us who bailed out of the plane over the jungle. Casey, he said... Quiet. Vasco had caused a lot of political trouble in his own country and he'd been told to stay out of it or else. They paid Chris Jonson and me a thousand bucks to fly him back there without anyone getting wise. We'd have done it if our plane hadn't gone wrong. But it did, and we had to jump. We were in luck, we thought, because all of us landed safely clear. Then, all of a sudden... Sykes, what was that?  It is a drum. Oh, that's not, Vasco. There's nothing but animals in this part of the jungle which are from the air. We're deep in the bush. Ah, look there. Yeah, guys with spears and claws. Indians. They are all around us clearly. You got the only gun, Sykes. Shoot. No, no, don't. The biggest man have laid down his spear and left his hand in a sign of peace. Sy, they're all laying down their weapons. It looked like they are coming as friends. They were friendly Indians. They took us to their village and treated us well. It seems we were the first white men they'd ever run into. An isolated tribe. The Vasco called them a lost tribe, Casey. They had houses built of stone and they acted civilized. That is outside of their religion. Their religion. They worship snakes. Now go on. Four constrictors were sacred to them. And they made human sacrifices to the poor. How? When anyone broke a law, they tied them up in big drums. After a while, a big snake had slid out of the jungle. I saw it done, but it didn't warn me. Let's have the rest, Helen. The top medicine man, the head priest of the tribe, had a good-looking daughter who felt for me hard. She had a bracelet of emeralds. Wait. After I picked up a little of her language, she told me where there were bigger, finer emeralds. I told Chris and Vasco what she'd said, so... one night the three of us started out. We must be getting close to the place she told you about, Sykes. As I get it from her, Chris, we'll find a long stone building completely hidden by jungle drought. A hundred-two-inch higher, Vasco. All right. I do not like these business Sykes. You're going to start that again. If they catch us before we can escape, well, you'll have to see what happened to men who break their law. They're not going to get me squeezed by any big snake, not while I have a gun. Listen, those drums... Right here. They're calling the big snake for the sacrifice tonight. Yeah, that's why I picked tonight to come here. The whole village will be attending the ceremony. You are sure nobody guards that temple where we go to? The girls says it's guarded only by the spirits. They won't bother us. We shall be robbing their temple. Oh, look. There is the long stone building. That's the place. You can walk right in. Sure, take what we want. Come on. It is so dark in there, and these torches give so little light. They'll give it up. The emeralds aren't back. On a statue, you said. Here, come on. I see. Holy snake. A big snake. Ron, get out.  It's the statue. The statue? Yes, Chris. A character of stone with a human face. Look, I see now. It has a woman's face.  And they're emerald necklace. We'll be millionaires, Chris. Oh, I'm envious. I'll climb up and get them. What's that? The drum. It started when you touched the snake's statue. Maybe. It's a warning. Fuck. Hand me a knife, Chris. Here. And be quick, Sykes. You are going to do what I came to do, Basker.  Pride the emerald eyes out. The three of us beat it fast. But when we slept, we dreamed of drums. That big statue of the serpent goddess. The snake with the woman's face. And sometimes deep in the jungle, we'd hear drums. Or think we heard them. Basker kept saying we'd never get away with what we'd done. He wanted his cut just like the rest of us. We kept on chopping our way through the tangled bush.  One day, when we lay down... There is no reason, Sykes, why you do not divide those emeralds now instead of waiting. I told you. Chris and I have ordered now. We're two to one. Yes, two to one. And every day we get closer to the edge of the jungle.  We ain't going to do nothing to you. Not a thing. It's your turn to scare up some grubs before you get at it. Why will you never lend me your pistol, Sykes?  I'm a good shot and I don't waste bullets and I'm saving the few I've got left. For what? For emergencies, of course. I see. Now get going. I'm hungry. I go. Listen to what? I don't hear nothing but birds. I hear drums. I don't hear any drums. You don't hear them now? No. There are no drum sounds. Maybe, maybe I hear them because I will be the first of us to pay for robbing the serpent goddess. I go to hunt for food. Guys drive a mean nuts, Chris. Me too. Sykes, you... you didn't hear no drum. No, I'm sure. Did you? I do not think so. I'm not over sure. You said maybe he heard them because he'll be the first of us to... Sykes! It's Fasca! Snake! Come away, Sykes! Run! Away, Chris! Away! I tried to help him. We knew it would be no use. We were afraid. Just left the guy to die. Yes, Casey. We did this run until we dropped and couldn't run anymore. Then the fever got us. I woke up in a village where the news reporters came and, well, Chris and I denied the true things we'd said while the fever was in our heads because... I can guess why you denied this story. Now she's followed us. She's paid off, Chris. And I'm next. I didn't see nothing in a paper today about the Johansson killing Casey. Hmm. Ain't Captain Logan going to arrest Sykes? What for? His alibi was 100%. Everybody confessed to stealing their memos. In another country, pal, from jungle Indians. Oh. There is one thing, Ethelbert, but it doesn't look very promising. What is it for you? Well, Logan's turned up a witness who says he saw Johansson let a woman into his apartment about a half hour before he was killed. A woman? Yeah, described as a small brunette and carrying a small leather traveling case. Oh, a little skinny girl couldn't squeeze a big guide at that. No. You think Sykes will be bumped off like Johansson was and that basket? Well, he seems to think so. That's funny. That guy's trying to pack a month of life into every hour because he figures every hour will be his last. Say, Annie, what do you say? Let's drop off at his new apartment on our way home. Maybe we can cheer him up a little. OK, Scout, if you must do a good deed. Well, it's a selfish good deed. I'd like to hear Sykes talk some more about that guy, Vaska. Oh, there's a parking spot, Casey, and back in that old Fort Coupe. That's for us. All right, somebody put a bad dent in the fender of that jalopy. I'll say. Sykes certainly got himself a swanky place to live when he moved out of that hotel. Whole first floor of these new garden apartments. Yep. I'll get you out of the car. OK. There's a light behind those Venetian blinds of the guys at home anyway. Let's go in. Ow! I am sorry. Excuse me. OK, sister, but what's your hurry? Well, she is in a hurry. I almost knocked you over and got into that old Fort. OK, so hers almost cracked my shin. She came out of Sykes' door. It's Annie. She was a small, pretty brunette with a traveling case. Casey. She and her porter out of site. Hey, look. Let's get into Sykes' apartment quickly. OK. Hey, hey, she didn't close the door tight. Nuts with ceremony in the bell. I'll open it myself. Sykes is lying on the floor. Just like Johansson. Hey, is he dead? He's dead all right. Oh, Casey. I think he's been squeezed to death. Oh. Just like Johansson. The serpent goddess. But that little brunette, she couldn't have crushed him. Don't see how. When gal's answering the same description or something. Huh. Where'd you just pick up? The valve cap off a tire. I wonder how that got here. Tire cap? Well, that won't help any. Hey, it's plenty help. Annie, pick up that phone and get your story into the paper. Yeah. I'm getting Logan at headquarters to tell him to locate an old Ford coupe with a dented rear fender. That's the car, Logan. I'm sure of it. The garage guy here says that Ford belongs to Miss Isabella Vaska. Is Isabella Vaska? Yes. I'm Captain Logan, homicide bureau. Remember me, Miss Vaska? It wasn't smart to use that dented car for a getaway after you murdered Sykes. I did not try to be careful or smart after my work was accomplished. I'm very tired. Please, take me to jail. You admit the killing of Sykes? I proudly admit it, but I am Pedro Vaska's sister. So that's the connection. Where is your brother, Miss Vaska? He never really believed he was killed by any human-faced bore constrictor. He wasn't. He got out of the jungle. And he wrote me a letter. Tell me about it. My brother was sure those men, Sykes and Johansson, intended to kill him.  He knew they would run away quick and leave him as I did. Then, alone, he made his way to a village at the edge of the jungle where he write to me of everything that was happening and asked me to avenge him. How did you do the job in such a fancy way, Miss Vaska? How did you crush those men to death? I know how she did that, Logan. You know his. I think so. Oh. First, I want to know why she did it. Why didn't your brother do his own avenging, Miss Vaska? Because when he wrote me that letter, he was dying. Just before he reached that village at the edge of the jungle, his body was broken in the coils of a big snake. We'll join the crowd at the Blue Note in just a moment. Very seldom do you hear a commercial announcement as important as the one we have for you tonight. It's about a brand new kind of dinnerware, a product of Anchor Glass. Its name is Jadite. J-A-D-E-I-T-E. Jadite. It looks and feels like rare Chinese porcelain.  And its cost is unbelievably low. Now, for instance, a beautiful Jadite cup and saucer costs only 15 cents. In fact, this revolutionary new Jadite costs less than half as much as the very cheapest dinnerware on the market. Now, you can buy Jadite items separately for a complete dinner service for six for less than five dollars. Now, the demand for Jadite is enormous. To avoid disappointment, go to the nearest chain store, department store, or other store selling Chinaware or Glass tomorrow and ask for Jadite by name. Jadite, J-A-D-E-I-T-E is the newest triumph of Anchor Hocking. The most famous name in Glass.  And how did you know? Well, that valve cap I found was a tip-off, Ethelbert. That and the suitcase she carried. And that suitcase contained a long, thick rubber tube and a portable electric air compressor pump. And Isabella Vaska is a pretty woman, Ethelbert. Both Sykes and Johansson were wolves.  You know, if a doctor ever used one of those blood pressure gadgets on your arm, pal, you know how air can squeeze. Of course, a doctor only uses a small bulb to pump it in a small tube. Gee, it was as simple as all that. Well, all this certainly wrecks the notion that that serpent goddess was paying off them three for stealing her emeralds. Does it, pal? Hmm? Think about it, Ethelbert. Gee. Gee. Time photographer starring Stott-Scotsworth as Casey is brought to you each Thursday by the Anchor Hocking Glass Corporation. Makers of Fire King Oven Glass. Anchor Glass Containers. Anchor Caps and Closures. All products of Anchor Hocking. The most famous name in glass. The original music is by Archie Blyer, and the program features Miss Jan Minor as Anne and John Gibson as Ethelbert. Herman Chittison is the Blue Note pianist. Help save lives by buying Christmas seals. These seals support the fight against tuberculosis. Buy and use Christmas seals and be sure to mail your packages early. This is Tony Marvin saying good night for the Anchor Hocking Glass Corporation of Lancaster, Ohio, the principal cities of the United States and Canada. Columbia Broadcasting System.


Now I am here to explain the features and pin diagram of microprocessor 8085 and 8086. At the end of this session, the student will be able to understand the features and pin diagram of microprocessor 8085 and 8086. So these are the contents, features of 8586, pin diagram of 8586, we will see one by one. So let us have a glance on features of 8085, it is an 8 bit microprocessor, it operates at plus 5 volt power supply and the operating frequency is 3 MHz, so which indicates that the time taken to complete one cycle is 1 by 3 MHz, that is equal to 0.33 microsecond. It has 16 address lines, 0 to A50 and data lines D0 to D7, next. As the address lines are 16 bit, it can access 64 kilobytes, that is 2 raise to 16, 6, 5, 5, 3, 6 bytes of memory. In the hex, it starts from 4 times 0 to 4 times H, it provides 8 bit input and output address, so that it can address 256 IOR devices. It supports 74 operations and 256 instructions, arithmetic and logic unit which performs addition, subtraction and logical operations such as AND, OR, XOR, COMPLEMENT and SHIFT operations. It has 8 bit general purpose registers such as B, C, D, E, H and L and 16 bit registers SP, PC, stack pointer, program counter and 8 bit accumulator, 8 bit flag register and instruction registers. Next, it provides 5 hardware interrupts such as TRAP, RS35.5, RS36.5, RS37.5 and INTR. It has serial input output control for serial communication and interrupt control to handle the interrupts. It provides control signals and it has an ability to share its system bus with direct memory access, DMA. It has two status signals S0 and S1. So, these are all about features of 8085. Next, we will see the features of 8086. It has an instruction queue which is capable of storing 6 instruction bytes from memory resulting in faster processing. It has 20 address lines and 16 data lines. It was the first 16 bit processor having 16 bit arithmetic and logic unit, 16 bit registers, internal data bus and 16 bit external data bus resulting in faster processing. It is available in three different versions depending on its operating frequency. 5 MHz, 8 MHz, 10 MHz. It uses two stages of pipelining, fetch stage and execute stage which improves the performance of pipelining. This stage can prefetch up to 6 bytes of instructions and stores them in the queue. Execute stage executes these instructions one by one. 86 is having 256 vector interrupts and 86 consists 29,000 transistors. So, these are the features of 8086. Now, think on this question and write the answer. Differentiate 8085 and 8086 microprocessor. Pause the video. I hope you have written the answer. So, the differences between 85 and 86 are like this. In terms of size, in the sense that 85 is a 8 bit microprocessor whereas 86 is a 16 bit microprocessor. 85 operates on 8 bit data, 86 operates on 16 bit data. Regarding address bus, 85 is having 16 bit address bus while 86 is having 20 address lines. Coming to memory part, 85 can access up to 64 kilobytes whereas 86 can access up to 1 MB of memory. Coming to instruction, 85 doesn't have an instruction queue whereas 86 is having an instruction queue which supports for 6 bytes. Coming to pipelining point, 85 doesn't support a pipeline architecture while 86 supports a pipeline architecture. Regarding input-output access, 85 can access 256 IO devices whereas 86 can access 65536 IO devices. Coming to cost, the cost of 85 is low whereas that of 86 is high. Coming to next diagram, a PIN diagram of 8085. So, 85 is having 40 PIN IC. So, these PINs are divided into different parts. These are low-order address bits, time-multiplexed with data bytes, high-order address bits and a few more PINs will go one by one detail. So, this notch is kept because to identify PIN number 1. With respect to this notch, left-side topmost PIN is PIN number 1. So, description of PINs. Address bus and data bus. Now, in this diagram, you will see the address bus and data. So, address bus AD0 to AD7, then next A8 to A15. So, AD0 stands address and data. So, these are multiplexed. This can be distinguished with the help of the PIN called ALE address latch enable. If this PIN is 1, then these AD PINs behave as an address. If it is 0, then it acts as a 0. Sorry, data. Control and status signals ALE, IO, M-bar, S0, S1, RD-bar, right-bar, ready. Next, power supply and clock frequency. VCC, VSS, VCC plus 5 volt, VSS ground reference, X1 and X2 are used as crystal to connect to get a frequency. Clock out. This signal can be used as a system clock for other devices. Interests and peripheral initiated signals. So, the interrupt, different interrupts are INTR, RST 7.5, 6.5, 5.5, trap. These are the different interrupts. And with respect to the INTR interrupt, so there is an acknowledgement called INTA, which indicates interrupt acknowledgement. Reset signals are used, such as reset in and reset out. So, reset in and which is active low, which is going to reset the microprocessor. Reset out is going to reset the connected devices. DMA stands direct memory access signals and here hold and hold acknowledgement. These are the concerned respective open names. So, hold is going to indicate that the external device is requesting the service of address and data. And HLDA is an acknowledgement of this hold. Serial input port and output port, SID and SOD. So, these are taking important role in case of serial communication. So, this is the PIN diagram of 8086. This is a 20 PIN IC. So, we will see all these one by one. So, it is having power supply and frequency signals. It uses 5 volt power supply and 5 megahertz, 8 megahertz, 10 megahertz. These are the frequencies at which it can operate. It is having address bus, data bus, address status bus. So, here in the diagram we can see the address and data bus AD02, here AD14, then 15, up to AD15, then A16 to A19. Total 20 address lines and data lines D02, D15, total 16 data lines. So, this is about address and data lines. Next, BHE and S7. This PIN, BHE stands for Bus High Enable, which is used to transfer data using the data lines DAA to D15. And the others PINs are ready, read, research in INTR, NMI, test, maximum mode, minimum mode. So, these are all concerned with minimum mode, PINs, hold, hold acknowledgement, right DT bar, MLE, INTA bar, etcetera. And these are concerned to maximum with respect to this hold from hold to INTA pin. All these S0, S7, S1, S2, QS0, QS1, RQ, etcetera. These are the references. Thank you.